Re: [protobuf] Re: Issue 515 in protobuf: More intelligent enums
The option suggested above could actually just append a prefix to the enum names that is an uppercase, underscore delimited name of the type. There should at least be the option to generate the enums that are locally scoped. Right now the only language that doesn't support it is an old version of C++ (C++03). The generated code in other languages is inconsistent with the rest of the code and makes code unreadable because the enum needs to be scoped once with the type and again using the prefix. Thanks Joe -- 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 protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/groups/opt_out.
[protobuf] Message and Field custom option conflict
I wanted to defined custom Field- and Message options by the same name
(having the same meaning but in different scope). For example:
v--
import descriptor.proto;
extend google.protobuf.FieldOptions {
optional bool aligned = 2000;
}
extend google.protobuf.MessageOptions {
optional bool aligned = 2000; // line 293
}
^--
This results in the following protoc error:
tst_protobuf.proto(293) : error in column=17: aligned is already defined
in tst_protobuf.
However, if remove the option from the MessageOptions and try to compile a
protocol with messages like:
v--
message test1
{
optional int64 fld = 10 [(aligned)=true];
}
message test2
{
option (aligned) = true;
optional int64 fld = 10;
}
^--
Then I will get an error depending on which of the custom 'align' options I
remove:
tst_protobuf.proto(293) : error in column=10: Option field (aligned) is
not a field or extension of message MessageOptions.
or
tst_protobuf.proto(298) : error in column=28: Option field (aligned) is
not a field or extension of message FieldOptions.
Is this a known/design limitation? Are there pattern in place for naming
the options according to where they are used (like 'message_alignment' vs.
'field_alignment')?
Regards,
Dror Harari
p.s. the original error is reported in descriptor.cc in AddSymbol...
--
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 protobuf+unsubscr...@googlegroups.com.
To post to this group, send email to protobuf@googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/groups/opt_out.
[protobuf] unable to compile once.h in solaris s10
functionclosure0 is not found. Error, nosemiheaderr: Use ; to terminate declarations. it is weird since compiler is generating error with the given google include files can some one help on this? -- 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 protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/groups/opt_out.
[protobuf] Issue 603 in protobuf: descriptor.proto: suggest add go_generic_services optional for golang.
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 603 by chaishus...@gmail.com: descriptor.proto: suggest add go_generic_services optional for golang. http://code.google.com/p/protobuf/issues/detail?id=603 In SVN r425, the go_package optional has been added to the descriptor.proto file [1]. Suggest add go_generic_services optional for golang RPC [2]. Reference: [1] https://code.google.com/p/protobuf/source/detail?r=425 [2] https://code.google.com/p/protorpc/ -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- 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 protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/groups/opt_out.
