[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#24949: Command-line argument parsing: named daemons

From: Philipp Stephani
Subject: bug#24949: Command-line argument parsing: named daemons
Date: Wed, 06 Sep 2017 18:32:18 +0000

Eli Zaretskii <address@hidden> schrieb am Mi., 6. Sep. 2017 um 20:05 Uhr:
> X-Spam-Status: No, score=1.1 required=5.0 tests=BAYES_50,
>       autolearn=disabled version=3.3.2
> From: Philipp Stephani <address@hidden>
> Date: Wed, 06 Sep 2017 17:33:33 +0000
> Cc: address@hidden
>  > Compare with something like "--chdir /tmp", where both forms (with and
>  > without "=") work.
>  I wouldn't expect it to work, since long options are documented to
>  need the equals sign.
> This is incredibly surprising and also inconsistent with the man page, which doesn't have equals signs for
> most options. Let's just document what everybody expects, i.e. that all options work with and without equals
> sign, and with one or two dashes.

Why would we want to do that?  Documentation should describe the
software, not our wishes.  If we want to change how the software
works, we should change the code first, and only after that change the
documentation.  Am I missing something here?

For almost all arguments all four variants (-foo bar, --foo bar, -foo=bar, --foo=bar) appear to work, for long and for short options. Either we should document that they work (that's what everybody expects by now), or turn the unwanted versions into explicit errors. 
We should generally change the code and the documentation at the same time, to make sure they are consistent.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]