Re: src/port/getopt_long.c lossy with arguments having no option characters - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: src/port/getopt_long.c lossy with arguments having no option characters
Date
Msg-id 551EEE5A.10709@gmx.net
Whole thread Raw
In response to Re: src/port/getopt_long.c lossy with arguments having no option characters  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: src/port/getopt_long.c lossy with arguments having no option characters  (Michael Paquier <michael.paquier@gmail.com>)
Re: src/port/getopt_long.c lossy with arguments having no option characters  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
On 4/3/15 10:08 AM, Tom Lane wrote:
> Michael Paquier <michael.paquier@gmail.com> writes:
>> The implementation of getopt_long in src/port has some limitations,
>> for example such commands do not work but they should:
>
> No, those should not work.  You're too used to versions that don't insist
> on switches-before-non-switch-arguments.  Such behavior is an extension
> that is not standard,

It is true that options after non-option arguments are a GNU extension,
but long options are also a GNU extension.  So the behavior we provide
is neither pure POSIX nor pure GNU.  I can see how that would be confusing.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: src/port/getopt_long.c lossy with arguments having no option characters
Next
From: Peter Slavov
Date:
Subject: Re: BUG #12910: Memory leak with logical decoding