Re: src/port/getopt_long.c lossy with arguments having no option characters
| От | Peter Eisentraut |
|---|---|
| Тема | Re: src/port/getopt_long.c lossy with arguments having no option characters |
| Дата | |
| Msg-id | 551EEE5A.10709@gmx.net обсуждение исходный текст |
| Ответ на | Re: src/port/getopt_long.c lossy with arguments having no option characters (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: src/port/getopt_long.c lossy with arguments having no
option characters
Re: src/port/getopt_long.c lossy with arguments having no option characters |
| Список | 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 по дате отправления: