Well, hackiness usually leads to deeper problems. For example, if there's
two ways to write the flag, then it's harder to grep for usages of it,
particularly if you aren't actually aware that there are multiple ways to
write it. I'm still leaning against this.
Anyone else have an opinion?
On
It would lead to an inconsistency with all of the other compiler
options that adhere to the underscore convention:
--decode_raw
--descriptor_set_out
--disallow_services
--include_imports
--proto_path
I think either all or none of them should be changed.
-dave
On Jan 12, 2:48 pm, Kenton Varda
(Personally, I prefer the GNU option format, so my vote is that if a
patch that passes muster is provided, it should be used).
-dave
On Jan 12, 3:11 pm, Dave Bailey d...@daveb.net wrote:
It would lead to an inconsistency with all of the other compiler
options that adhere to the underscore
I'm for changing it. Command line flags get deprecated in software
all the time.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To post to this group, send email to protobuf@googlegroups.com
On Mon, Jan 12, 2009 at 5:27 PM, Alek Storm alek.st...@gmail.com wrote:
I'm for changing it. Command line flags get deprecated in software
all the time.
Only for good reasons. This isn't a good enough reason to deprecate. So
the options are between having just the underscore versions or
