Which is the best and why

[Brayden Evans]

...

[Lucas Collins]

Definitely not the last.

[Adrian Clark]

First one is an abbreviation of the second. Third is trash.

[Nolan Foster]

GNU style is the only one that makes sense.

--afunctionality
--bfunctionality
--cfunctionality
or
-a
-b
-c

with the possibility to do
-abc

[Isaac Rogers]

GUI

[Wyatt Price]

I wish more software did this rather than some half ass abomination.

[Adrian Ward]

-arg
Please and thank you, short, sweet, and simple.

[Jacob Price]

Master race

[Ian Garcia]

>arg
>white

[Lucas Allen]

/thread

[Nathaniel Morales]

This

[Asher White]

this. -a or --arg

[Cameron Mitchell]

This tbqh.

[Blake Hall]

This, 100%

[Lincoln Cooper]

Is there any reason why we have both - and --? It seems - would be simpler and shorter.

[Logan Richardson]

Do you mean --thread ??? ^^

[Carter James]

- for single-letter bool flags
-- for arguments which should be a short word followed by a value

[Tyler Parker]

legibility
say you want to write a shell script using tools you almost never use.
It's easier to read said script few years in the future without having to refer to the manpage

[Eli Carter]

Only
ARG=VALUE ./a.out
is patrician

[Jackson Hernandez]

I'll admit, I both keked, and cursed you for thinking of that when I didn't

[Cooper Wilson]

This is the best.

[Levi Cook]

I hate --arg and I don't understand /arg

-arg is best

[Gabriel Walker]

how do you use it in an automated script?

[Charles Clark]

If your operating system isn't stuck in the previous century, then there are tools like Visual Studio Coded UI.

>yfw freetards haven't progressed past the text line interface because they think GUIs can't be automated

[Kayden Powell]

obviously

[Sebastian Baker]

duh... you obviously make the script select the window named "app", type whatever you want as the argument and then presses enter

[Parker Watson]

Program has arguments o, t, u and out.
Is -out o, u and t or out?

[Angel Hughes]

Right, but GNU style seems to include weird conventions for options with arguments.

-Wall

Is that one option -Wall that just uses a single hyphen? Is it four options -W -a -l -l? No, it's one option -W with the argument all. But there's no way to tell.

The sane way would be to put a space, or maybe an equals for long options. -W all or --warning=all.

I think getopt_long() is pretty flexible, but it does seem like there's an ambiguous case. I guess it must have some way to tell the difference between -W all and -W -a -l -l.