Comment #4 on issue 183 by t.broyer: --java_out=output_list_file= parameter
fails when compiling multiple proto files
http://code.google.com/p/protobuf/issues/detail?id=183
In the event you'd like to fix this anyway, it might be as easy as adding a
new
method to CodeGenerator:
public:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 184 by h.a.syed: C++ Strange Memory Warning Under Visual Studio
2008 SP1 on Windows 7
http://code.google.com/p/protobuf/issues/detail?id=184
What steps will reproduce the problem?
1. Compile a protobuf object in an
A single message type can be used as both a message and as a group, so there
is no way to tell which it is from the Descriptor. You have to have the
FieldDescriptor in the containing message.
On Thu, Apr 29, 2010 at 1:36 PM, adamdms adam.kwintkiew...@gmail.comwrote:
how to check whether the
hmm this is a slight problem. I am iterating over the nested messages and
then generating a message/group code. I don't have reference to the specific
field
2010/4/29 Kenton Varda ken...@google.com
A single message type can be used as both a message and as a group, so
there is no way to tell
Why do you need to generate different code for the two? All the official
code generators generate exactly the same code for message classes whether
they be nested messages or groups. Version 1 of protocol buffers generated
different classes and it proved to be an enormous pain.
On Thu, Apr 29,
They have different wire type (2; 3 and 4). They are stored in different
ways and because of that they have a little bit different code inside
parsing/serializing methods.
2010/4/29 Kenton Varda ken...@google.com
Why do you need to generate different code for the two? All the official
code
