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

From Tom Lane
Subject Re: src/port/getopt_long.c lossy with arguments having no option characters
Date
Msg-id 2737.1428097651@sss.pgh.pa.us
Whole thread Raw
In response to Re: src/port/getopt_long.c lossy with arguments having no option characters  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: src/port/getopt_long.c lossy with arguments having no option characters  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
Michael Paquier <michael.paquier@gmail.com> writes:
> On Sat, Apr 4, 2015 at 4:47 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
>> 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.

> Well, OK. Then we had better update a bit the TAP tests of initdb and
> createdb because they break on any platform which is not compliant
> with that.

If those tests are dependent on behavior we don't document as allowed,
I think we should change the tests.  Want to send a patch?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: src/port/getopt_long.c lossy with arguments having no option characters
Next
From: Alvaro Herrera
Date:
Subject: Re: src/port/getopt_long.c lossy with arguments having no option characters