Anyone know why generated C# classes don't include the named constants for
options? (MessageOptions,FieldOptions,etc).
They still work but you have to hard code the number value directly, which
is less that readable and isn't on par with the named constants generated
for the C++ files.
--
Is it possible to add a field option to select fields within an imported
message? Ie without modifying the original proto file, add custom options to
its fields?
Thanks
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To unsubscribe from
I don't understand. If a message is a simple struct then the generated wrapper
code would populate it with the default as defined by the proto it was compiled
with wouldn't it? Are you suggesting that the implementation on different
platforms would lack the wrapper objects generated by
That sounds like a poor design decision, and one easily readded without
breaking anything. If a field doesn't have an explicit default, you use 0 or
whatever, thereby not breaking anyone not using them, but if an explicit
default is provided that is used instead. I am using that feature as
Does the arena allocator also get used by messages allocated as children of the
root message?
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Is it possible, given a proto file, but without compiling it(protoc), to use
the proto file directly to be able to load data? In other words parsing the
proto file at run time and generating a reflection interface or something such
that a tool may read the messages with just the proto file
What about something like this
message UnknownMessage
{
enum MessageType
{
MESSAGE_TYPE_A = 1;
MESSAGE_TYPE_B = 2;
MESSAGE_TYPE_C = 3;
}
required MessageTypemsgType = 1;
required bytesmsgPayload = 2;
}
On Wednesday, February 10,
I know the answer is that it doesn't support this, but here's what I'm
wanting to set up to give a clearer view.
Suppose you have a set of nested messages that represent the application
state of an entire application, in this case a game and its entities and
various other stuff. Here's a
Is there a way to tell the proto compiler to generate message definitions
for which the message fields are statically defined rather than each
individual field allocated with dynamic memory? Obviously the repeater
fields couldn't be fully statically allocated(unless you could provide the
