Here's a basic .proto I'm currently using:
package levelFormat;
message vec3
{
optional float x = 1;
optional float y = 2;
optional float z = 3;
}
message quat
{
optional float x = 1;
optional float y = 2;
optional float z = 3;
optional float w = 4;
}
message entity
Can you write a small example program demonstrating your problem? I can
then debug it.
On Sun, May 3, 2009 at 8:33 AM, wrote:
> PS. is there a reason the compiler turns camelCaseFields into
> noncamelcasefields, but messageNamesAreStillPreservedWithCamelCase?
Historical reasons. In the early
Unfortunately these kinds of problems are considered outside the scope of
what the Protocol Buffers library provides. You will need to devise some
sort of container format which implements the features you want. You can
still use protobufs to encode individual messages, and then have your
contain
