[protobuf] [PATCH] Display non-present fields with TextFormat.

2010-11-23 Thread Brenden Matthews
oup/protobuf?hl=en. From edf13be13766caa1a496c9feeced8d9d24de0c10 Mon Sep 17 00:00:00 2001 From: Brenden Matthews Date: Tue, 23 Nov 2010 17:01:01 -0800 Subject: [PATCH] Display non-present fields with TextFormat. This allows for the non-presence of optional fields to be represented in string ou

[protobuf] Re: [PATCH] Display non-present fields with TextFormat.

2010-11-23 Thread Brenden Matthews
On Tue, Nov 23, 2010 at 5:04 PM, Brenden Matthews wrote: > Greetings, > > One of the best features of protocol buffers is the notion of presence. > Another great feature is the ability to do 'message.PrintDebugString()'. > One problem, however, is that fields which a

Re: Message::ByteSize() wrong

2009-10-07 Thread Brenden Matthews
On Wed, Oct 7, 2009 at 6:48 PM, Henner Zeller wrote: > Still haven't run it (I only seem to have a too old cmake; a simple > Makefile with a .proto and .cc file showing the problem would be > better. Please strip down the example if someone should help debugging > it ;) ) > > Anyway, it seems tha

Re: Message::ByteSize() wrong

2009-10-07 Thread Brenden Matthews
On Wed, Oct 7, 2009 at 6:24 PM, Henner Zeller wrote: > Hi, > haven't run the example yet, just a quick look (however, it is a bit > more than a stripped example of the problem ;) ) > > You have some constants strayed in such as > size_t len = msg.GetCachedSize() + 6; > why that ? > > -h

Re: Message::ByteSize() wrong

2009-10-07 Thread Brenden Matthews
Oops, had some bad math in that last sample. This is more correct (but still fails). On Wed, Oct 7, 2009 at 5:33 PM, Brenden Matthews wrote: > Here you go...attached is an example that fails quite reliably (for me). > Compile like so: > > mkdir build > cd build > cmake ../

Re: Message::ByteSize() wrong

2009-10-07 Thread Brenden Matthews
n. Can you provide a complete example program that > demonstrates your problem? > On Wed, Oct 7, 2009 at 4:01 PM, Brenden Matthews wrote: > >> >> The value returned by Message::ByteSize() does not match the actually >> number of bytes that are consumed after writ

Message::ByteSize() wrong

2009-10-07 Thread Brenden Matthews
The value returned by Message::ByteSize() does not match the actually number of bytes that are consumed after writing a message to a stream. Example: some_message m; /* ... populate m ... */ size_t len = m.ByteSize(); int pos = boost::iostreams::position_to_offset(stream.tellp())

Large data sets

2009-10-06 Thread Brenden Matthews
Hi, In the documentation here: http://code.google.com/apis/protocolbuffers/docs/techniques.html#large-data it specifies that "if you are dealing in messages larger than a megabyte each, it may be time to consider an alternate strategy". My question is: does this apply to messages which are lar

Re: Default Instances -> Memory Leaks?

2009-09-30 Thread Michael Matthews
I'm using VC++ 8.0+ with protobuf 2.2.0 and as long as I add the call toShutdownProtobufLibrary() before exiting I don't see any memory leaks. Michael Matthews On Wed, Sep 30, 2009 at 8:45 AM, Peter K. wrote: > > Hi All, > > I'm using protocol buffers under Visual C+

Re: CodedOuptputStream.PushLimit/PopLimit

2009-06-30 Thread Matthews
The title should have been CodedInputStream.PushLimit/ PopLimitsightyping too fast. Thanks for your patience. Michael --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this

CodedOuptputStream.PushLimit/PopLimit

2009-06-30 Thread Matthews
I am writing a Java server and C++ client and trying to use Protocol Buffers for encoding the socket communication. I have written the Java server and tested it with a Java based client and all is well. However, I am having some difficulty with the C++ portion. I've wrapped the socket code in my