[protobuf] Issue 509 in protobuf: import public generates wrong python code

Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 509 by pyro...@gmail.com: import public generates wrong python code http://code.google.com/p/protobuf/issues/detail?id=509 What steps will reproduce the problem? 1. Put all 3 attached files in one folder 2. R

[protobuf] Issue 510 in protobuf: Make fails on FreeBSD 9.0

Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 510 by peter.robinett: Make fails on FreeBSD 9.0 http://code.google.com/p/protobuf/issues/detail?id=510 What steps will reproduce the problem? 1. portsnap fetch; portsnap update 2. cd /usr/ports/net/mosh 3. make

[protobuf] Re: Issue 510 in protobuf: Make fails on FreeBSD 9.0

Comment #1 on issue 510 by ande...@mit.edu: Make fails on FreeBSD 9.0 http://code.google.com/p/protobuf/issues/detail?id=510 The similar report at http://forums.freebsd.org/archive/index.php/t-28304.html suggests that you may have run out of disk space during the compile? -- You received t

[protobuf] Re: Issue 510 in protobuf: Make fails on FreeBSD 9.0

Comment #2 on issue 510 by peter.robinett: Make fails on FreeBSD 9.0 http://code.google.com/p/protobuf/issues/detail?id=510 My main partition has 50% (7 GB) free, though there isn't a lot of free memory (200 MB). Reading more from that link, the machine was out of swap space: `pid 2794 (cc1p

[protobuf] protobuf 2.5.0 linux version mismatch

I tried to build protobuf 2.5.0 on linux - ubuntu kernel 2.6.32 but the protoc executable file with the command --version give the result ver 2.2.0 -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop re

[protobuf] [compiler] Enforcing backward compatibility rules

Hi, To maintain backward compatibility with released .proto definitions, there are certain rules that needs to be followed while extending them(they are well documented). I am wondering if there are existing tools that enforce these rules by comparing the released .proto files. May be the pro

[protobuf] Can I use int16 instead of int32 to verify a variable？

Hi, I have a question here, I want use int16 (short) to verify a variable,because int32 is too big for me , I want to reduce the length of my package. Is there any way to do this? Thank you ! -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group.

[protobuf] Export Control information for Protobuf

Hello; Our product uses Protobuf v2.4.0, and to expand its market we need to perform Export Control for our product software. Is there an ECCN and/or CCATS or any other export control designation for this component? If not, does this component perform any encryption (other than that used fo

Re: [protobuf] Can I use int16 instead of int32 to verify a variable？

On Thu, Apr 25, 2013 at 9:36 PM, 王海龙 wrote: > Hi, > I have a question here, > I want use int16 (short) to verify a variable,because int32 is too big for > me , I want to reduce the length of my package. > What do you mean by "the length of your package"? I believe using int16 doesn't save you any

Re: [protobuf] protobuf 2.5.0 linux version mismatch

On Tue, May 7, 2013 at 2:20 AM, wrote: > I tried to build protobuf 2.5.0 on linux - ubuntu kernel 2.6.32 > but the protoc executable file with the command --version give the result > ver 2.2.0 You are probably calling the one coming with the system, not the one you built. > > > > > -- > You r

Re: [protobuf] Export Control information for Protobuf

On 7 May 2013 19:40, "Marc Gravell" wrote: > I don't know about the other stuff. But: protobuf does not include any > form of encryption. Since it only handles serialization (not full RPC) it > does not include any authentication logic either. The data is serialized > without encryption - althoug

Re: [protobuf] Can I use int16 instead of int32 to verify a variable？

On 7 May 2013 18:53, "Marc Gravell" wrote: > Protobuf has a fee encodings for integer data, which basically come down > to: > > - varint (with or without zigzag) > - fixed-32 (always 4 bytes) > - fixed-64 (always 8 bytes) > > For 16 bits, you will do best with varint. If the data can be negative

[protobuf] Using enum as extension id?

Is it possible to define an extension and use an enum value as the extension id? Say with the following files defined: *file: MessageType.proto:* enum MessageType { MSG_TYPE_1 = 100; MSG_TYPE_2 = 101; } *file: AMessage.proto:* import "MessageType.proto"; message AMessage { requi

Re: [protobuf] protobuf 2.5.0 linux version mismatch

Yes, I've just found the solution. It's a bit strange, because after make (make install) command there are two different exacutable file protoc in ./src the old 2.2.0 and the correct one 2.5.0 in the installation directory. In any case thanks now it works. Federico On Tuesday, May 7, 2013 7: