Re: [protobuf] how to get RepeatedField object

2010-02-16 Thread Kenton Varda
On Tue, Feb 16, 2010 at 2:47 PM, Romain Francois < romain.francois.r.enthusi...@gmail.com> wrote: > Thanks for the feedback. > > > On 02/16/2010 10:44 PM, Kenton Varda wrote: > >> GeneratedMessageReflection is an internal class used by the protobuf >> implementation. Currently, users are not allo

Re: [protobuf] how to get RepeatedField object

2010-02-16 Thread Romain Francois
Thanks for the feedback. On 02/16/2010 10:44 PM, Kenton Varda wrote: GeneratedMessageReflection is an internal class used by the protobuf implementation. Currently, users are not allowed to use it directly, because we may change it at any time. You're suggesting that we promote it to a public

[protobuf] Re: Issue 165 in protobuf: can not link for mips architecture

2010-02-16 Thread protobuf
Updates: Status: Accepted Owner: ken...@google.com Comment #4 on issue 165 by ken...@google.com: can not link for mips architecture http://code.google.com/p/protobuf/issues/detail?id=165 I believe we should try to detect this problem in stl_hash.m4, and fall back to hash_map

Re: [protobuf] how to get RepeatedField object

2010-02-16 Thread Kenton Varda
GeneratedMessageReflection is an internal class used by the protobuf implementation. Currently, users are not allowed to use it directly, because we may change it at any time. You're suggesting that we promote it to a public interface, which has implications with regard to maintenance costs and i

Re: [protobuf] help with protoc --decode required

2010-02-16 Thread Kenton Varda
Does your .proto file define a package? E.g. if you have: package foo.bar; message Manager { ... } Then you need to do: protoc --decode=foo.bar.Manager manager.proto < input On Sat, Feb 13, 2010 at 2:54 PM, Geoffrey wrote: > Hi, > > Does someone have an example of protoc with --decode option

Re: [protobuf] Java Protocol Buffers classes serialization

2010-02-16 Thread Kenton Varda
On Sun, Feb 14, 2010 at 4:36 AM, Jaroslaw Odzga wrote: > I'll have to disagree :-) Serialization is not a way of mutating objects > and Externalizable is thought to be just an efficient Serialization. > readExternal() is not a public method anyway. Since Externalizable is an interface, all its m