From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, noah(at)leadboat(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: add non-option reordering to in-tree getopt_long |
Date: | 2023-12-19 16:44:52 |
Message-ID: | 20231219164452.GA832556@nathanxps13 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Dec 18, 2023 at 09:31:54PM -0500, Tom Lane wrote:
> Agreed, if it actually is 19 years old. I'm wondering a little bit
> if there could be some moderately-recent glibc behavior change
> involved. I'm not excited enough about it to go trawl their change
> log, but we should keep our ears cocked for similar reports.
From a brief glance, I believe this is long-standing behavior. Even though
we advance optind at the bottom of the loop, the next getopt_long() call
seems to reset it to the first non-option (which was saved in a previous
call).
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jelte Fennema-Nio | 2023-12-19 16:47:42 | Re: Add new for_each macros for iterating over a List that do not require ListCell pointer |
Previous Message | Nazir Bilal Yavuz | 2023-12-19 16:44:48 | Re: Remove MSVC scripts from the tree |