Thanks.
I downloaded the binaries and tried to use the test class but my
compiler couldn't see class protobuf.codec.json.TypesProtoBuf, it's
not anywhere in the binaries. Has this class been added recently but
was not reflected to the binaries? I also tried to download source,
but seems like GIT i
Hi, all,
I've uploaded release candidate 2.4.0rc1 here:
http://protobuf.googlecode.com/svn/rc/
Feel free to test it out. Feedbacks are highly appreciated (please
include what platform you use, and whether or not it worked).
--
You received this message because you are subscribed to the Google
On Tue, Jan 4, 2011 at 5:25 PM, Igor Gatis wrote:
> A while ago, a colleague had a "memory leak" reusing a PB message which
> contained a repeated field. If I'm not mistaken the problem was that
> pb_message::Clear() calls vector::clear() and string::clear()
> which does not really release the me
On Jan 4, 2011, at 20:25 , Igor Gatis wrote:
A while ago, a colleague had a "memory leak" reusing a PB message
which contained a repeated field. If I'm not mistaken the problem
was that pb_message::Clear() calls vector::clear() and
string::clear() which does not really release the memory all
On Tue, Jan 4, 2011 at 9:38 PM, Kenton Varda wrote:
> I think this would be too complicated to integrate into the official C++
> implementation. You could, however, write an alternative protobuf
> implementation that provides this.
>
> Note that with the official implementation, you can avoid ma
Comment #35 on issue 188 by ken...@google.com: protobuf fails to link after
compiling with LDFLAGS="-Wl,--as-needed" because of missing -lpthread
http://code.google.com/p/protobuf/issues/detail?id=188
Thanks!
--
You received this message because you are subscribed to the Google Groups "Proto
The author of protobuf-c might not read this list. You might want to e-mail
him directly.
But I would suggest looking at the contents of tut.pb-c.c to see whether it
actually defines a_message__pack. Maybe the problem will be obvious.
On Tue, Dec 28, 2010 at 3:08 PM, Suhail Doshi wrote:
> I am
I think this would be too complicated to integrate into the official C++
implementation. You could, however, write an alternative protobuf
implementation that provides this.
Note that with the official implementation, you can avoid malloc costs by
reusing message objects. A message object never
