Endian

I quickly reviewed the documentation and the faq and found no reference to the protocol demanding big endian or little endian or associated byte order conversion. Does the protocol require one or the other? Alternately, does the compiled have an endian switch/ conversion option in the resulting

Re: Core Dump with c++ 4.1.1

Sushil Shelly wrote: Kenton and Team, We recently moved to using c++ 4.1.1 and are getting a segmentation fault as shown below. We are simply building the tutorial code and then run 'add_person' (This same test runs fine when built with C++ 3.4.0). Did you re-build protobuf after upgrading

Re: Core Dump with c++ 4.1.1

Yea we do a make clean and rebuild to get new libraries, Is there any one actually using C++ 4.1.1? On Fri, Aug 14, 2009 at 11:59 AM, Monty Taylor mord...@inaugust.com wrote: Sushil Shelly wrote: Kenton and Team, We recently moved to using c++ 4.1.1 and are getting a segmentation fault

Re: Core Dump with c++ 4.1.1

Sushil Shelly wrote: Yea we do a make clean and rebuild to get new libraries, Is there any one actually using C++ 4.1.1? By C++ 4.1.1 I'm assuming you are using GCC? If so, yes, I use this on several of the machines in my build farm for Drizzle (which uses Protobuf quite heavily) with no

Re: Endian

On Fri, Aug 14, 2009 at 8:28 AM, DavePpelow...@pelowitz.com wrote: I quickly reviewed the documentation and the faq and found no reference to the protocol demanding big endian or little endian or associated byte order conversion.  Does the protocol require one or the other?  Alternately,

Re: Endian

The encoding documentation: http://code.google.com/apis/protocolbuffers/docs/encoding.html http://code.google.com/apis/protocolbuffers/docs/encoding.htmlspecifies that fixed-width numbers are encoded in little-endian order. However, you only have to know that if you are writing a protobuf parser

Re: protobuf HPUX support

Thanks. In order to accept this I'll need you to sign the Contributor License Agreement: http://code.google.com/legal/individual-cla-v1.0.html -- If you own copyright on this patch. http://code.google.com/legal/corporate-cla-v1.0.html -- If your employer does. You can sign the individual

combine protobuf messages

Hi, I have a following use case and I'm not sure what will be the best way to go. I have a relatively complex protobuf message that I'm using in my application. It should be correctly initialized my application to works. The problem I have is that the information that makes this complete

Re: combine protobuf messages

On Fri, Aug 14, 2009 at 1:18 PM, George Georgiev georgi.georg...@citrix.com wrote: 1. How to serialize parts from the message without validation Use the Partial serialization and parsing methods, e.g. SerializePartialToString() and ParsePartialFromString(). These do not check required

RE: combine protobuf messages

Hi, MergeFrom sounds good. The only issue that I still will have is with the repeated fields. For some of them I will have an Id attribute. So what I would like to achieve is when I merge the messages instead of adding new partial message in the list it to combine those of the repeated

Re: combine protobuf messages

If you can just write code specific to your message type which deals with merging items with the same ID, I'd suggest doing that. If you really need to write a totally generic algorithm, you can use reflection as documented here: