| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: src/port/getopt_long.c lossy with arguments having no option characters |
| Date: | 2015-04-03 21:47:31 |
| Message-ID: | 2737.1428097651@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> On Sat, Apr 4, 2015 at 4:47 AM, Peter Eisentraut <peter_e(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-04-03 22:06:38 | Re: src/port/getopt_long.c lossy with arguments having no option characters |
| Previous Message | Michael Paquier | 2015-04-03 21:41:59 | Re: src/port/getopt_long.c lossy with arguments having no option characters |