Re: POSIX long command line arguments

2009-01-13 Thread David Biesack
(I certainly meant all options with underscores; I just cited two for brevity.) The other thing to consider here is when new options need to be added; if hyphens are not adopted now, "consistency" will mean new options will also use underscores. -djb --~--~-~--~~~---

Re: POSIX long command line arguments

2009-01-12 Thread Kenton Varda
On Mon, Jan 12, 2009 at 5:27 PM, Alek Storm 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 accepting both unde

Re: POSIX long command line arguments

2009-01-12 Thread Alek Storm
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.co

Re: POSIX long command line arguments

2009-01-12 Thread Dave Bailey
(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 wrote: > It would lead to an inconsistency with all of the other compiler > options that adhere to the underscore convention: > >

Re: POSIX long command line arguments

2009-01-12 Thread Dave Bailey
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

Re: POSIX long command line arguments

2009-01-12 Thread Kenton Varda
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 Mon

Re: POSIX long command line arguments

2009-01-12 Thread David Biesack
As a user, I'm less concerned with the internal hackiness level, more so with the consistent interface :-) The code is clean enough to support both, it appears. I'd vote for it; I can contribute some code if you like. On Jan 12, 2:08 pm, Kenton Varda wrote: > Hmm, you're probably right that the

Re: POSIX long command line arguments

2009-01-12 Thread Kenton Varda
Hmm, you're probably right that the arguments should have used hyphens rather than underscores. That said, we certainly can't just change it without breaking people, and accepting both seems hacky. On Mon, Jan 12, 2009 at 10:19 AM, David Biesack wrote: > > Has there been any thought to adopting

POSIX long command line arguments

2009-01-12 Thread David Biesack
Has there been any thought to adopting more conventional style GNU/ POSIX command line argument notation, i.e. --java-out and --proto-path instead of --java_out and -- proto_path? The underscores always trip me up. reference: http://www.gnu.org/prep/standards/standards.html#Option-Table where '-'