[protobuf] Re: Issue 60 in protobuf: Support static values in .proto files

2014-10-06 Thread protobuf
Updates: Status: WontFix Comment #12 on issue 60 by xiaof...@google.com: Support static values in .proto files https://code.google.com/p/protobuf/issues/detail?id=60 (No comment was entered for this change.) -- You received this message because this project is configured to send all

[protobuf] Re: Issue 60 in protobuf: Support static values in .proto files

2014-10-06 Thread protobuf
Comment #13 on issue 60 by e...@rjump.com: Support static values in .proto files https://code.google.com/p/protobuf/issues/detail?id=60 Is there somewhere that explains the reasoning behind not wanting this? Is there another option/approach/design that resolves this need? -- You received

[protobuf] Re: Issue 60 in protobuf: Support static values in .proto files

2014-10-06 Thread protobuf
Comment #14 on issue 60 by xiaof...@google.com: Support static values in .proto files https://code.google.com/p/protobuf/issues/detail?id=60 For every new feature we always consider its benefit against the complication it adds to protobuf API and we usually weigh API complications much

[protobuf] Re: Issue 60 in protobuf: Support static values in .proto files

2013-01-27 Thread Chen Feng
1. more plain and then readable code package::CONSTANT_NAME vs package::Constants::default_instance().constant() 2. compile time const is irreplaceable for many C++ code, such as array bound and template value parameter. 3. safety, default value can be changed careless. 在

[protobuf] Re: Issue 60 in protobuf: Support static values in .proto files

2013-01-25 Thread moofish
Field options can provide this capability unless you are really looking for the ability to just not type the same value? I would think the default value and field options would work. It is possible I don't fully understand your use case. On Thursday, January 24, 2013 9:23:39 AM UTC-8,

[protobuf] Re: Issue 60 in protobuf: Support static values in .proto files

2013-01-24 Thread protobuf
Comment #11 on issue 60 by chen3f...@gmail.com: Support static values in .proto files http://code.google.com/p/protobuf/issues/detail?id=60 Support constant in proto is very useful const int64 DefaultType = 1000; optional int64 type = 1 [default=DefaultType]; -- You received this message

[protobuf] Re: Issue 60 in protobuf: Support static values in .proto files

2012-01-20 Thread protobuf
Comment #10 on issue 60 by anish...@gmail.com: Support static values in .proto files http://code.google.com/p/protobuf/issues/detail?id=60 But even though it had getters and setters, here need only the getters.. -- You received this message because you are subscribed to the Google Groups

[protobuf] Re: Issue 60 in protobuf: Support static values in .proto files

2011-01-03 Thread protobuf
Comment #8 on issue 60 by mer...@google.com: Support static values in .proto files http://code.google.com/p/protobuf/issues/detail?id=60 I've been wishing for this once in a while. There's a workaround: Protobuf actually does have a syntax for literal values: field defaults. So you can