On Fri, May 4, 2012 at 9:07 AM, Sami Kerola <kerolasa@xxxxxx> wrote: > On Fri, May 4, 2012 at 2:29 AM, Craig Small <csmall-procps@xxxxxxxxxx> wrote: >> This is my #1 thing I hate about glibc. Non-optional argument >> is -p foo but optional has to be -pfoo. When I first saw this I >> thought it was typical PHP brokenness but its not (for once) >> its glibc brokeness. > > Hating glibc because of optional arguments is probably fair. > > http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html#tag_12_02 > > 'Guideline 7: > Option-arguments should not be optional.' > > And the same is in IEEE Std 1003.1-2001 which the glibc getopt() > claims to be compliant with. > > I wonder if the sysctl -p should not take optional argument, > but let the command arguments to deal the files. Comments? The related change could look something like this