mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Haelwenn (lanodan) Monnier" <contact@hacktivis.me>
To: musl@lists.openwall.com, Thorsten Glaser <tg@mirbsd.de>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [musl] getpass() feature test macro
Date: Fri, 11 Jul 2025 02:58:04 +0200	[thread overview]
Message-ID: <aHBhnP91d6AWmGKl@cloudsdale.the-delta.net.eu.org> (raw)
In-Reply-To: <aHBe00QWQ4lfJL72@cloudsdale.the-delta.net.eu.org>

[2025-07-11 02:46:11+0200] Haelwenn (lanodan) Monnier:
>[2025-07-09 19:56:14-0400] Rich Felker:
>>On Thu, Jul 10, 2025 at 12:20:42AM +0200, Thorsten Glaser wrote:
>>> On Wed, 9 Jul 2025, Thomas Petazzoni wrote:
>>>
>>> >               _XOPEN_SOURCE && ! (_POSIX_C_SOURCE >= 200112L)
>>>
>>> This looks like a bug: a search for getpass in POSIX returns
>>> no match.
>>
>>It was probably in an older version of POSIX (possibly XSI shaded, not
>>sure). Generally we don't provide full compat with older versions of
>>the standards, since it turns into a mess of version conditions and
>>programs using a mix of older stuff are usually better off just with
>>_DEFAULT_SOURCE (alias _BSD_SOURCE). There are a few exceptions for
>>stuff that's still widely used like gethostby* that recent standards
>>removed, but I'm not sure it would make sense to treat getpass special
>>like that being that it's a rarely used and IIRC removed a long time
>>ago.
>>
>>Rich
>
>getpass() was in SUSv2 but already marked legacy: https://pubs.opengroup.org/onlinepubs/007908799/xsh/getpass.html
>
>SUSv2 uses _POSIX_C_SOURCE 199506L: https://pubs.opengroup.org/onlinepubs/007908799/xsh/compilation.html
>
>And expectedly, SUSv3 removed it: https://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap01.html
>
>Which uses _POSIX_C_SOURCE 200112L: https://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_02.html

PS: Looking at the PDFs, it has EX shading (extension, seems like early form of XSI shading); so feature macro should be (_XOPEN_SOURCE < 600).
But `_XOPEN_SOURCE && ! (_POSIX_C_SOURCE >= 200112L)` seems okay, just potentially misleading due to the !

Best Regards

  reply	other threads:[~2025-07-11  0:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 21:52 [musl] getpass() feature test macro Thomas Petazzoni
2025-07-09 22:20 ` Thorsten Glaser
2025-07-09 23:56   ` [musl] " Rich Felker
2025-07-10  7:55     ` Thomas Petazzoni
2025-07-10 15:54       ` Rich Felker
2025-07-10 15:56         ` Thomas Petazzoni
2025-07-10 16:01           ` Rich Felker
2025-07-10 16:13             ` Thomas Petazzoni
2025-07-10 16:40               ` Rich Felker
2025-07-11 19:16               ` Thorsten Glaser
2025-07-11  0:46     ` [musl] " Haelwenn (lanodan) Monnier
2025-07-11  0:58       ` Haelwenn (lanodan) Monnier [this message]
2025-07-11  1:18         ` A. Wilcox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aHBhnP91d6AWmGKl@cloudsdale.the-delta.net.eu.org \
    --to=contact@hacktivis.me \
    --cc=musl@lists.openwall.com \
    --cc=tg@mirbsd.de \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).