From: Florian Weimer <fw@deneb.enyo.de>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: libc-alpha@sourceware.org
Subject: Re: posix_openpt vs getpt??
Date: Tue, 31 Dec 2019 14:25:37 +0100 [thread overview]
Message-ID: <87a778mxta.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20191230213550.icqt2er7dwnxcrrb@function> (Samuel Thibault's message of "Mon, 30 Dec 2019 22:35:50 +0100")
* Samuel Thibault:
> In sysdeps/unix/bsd/getpt.c we can read:
>
> /* We cannot define posix_openpt in general for BSD systems. */
>
> I do not see why posix_openpt can't be defined like getpt is. Is there
> a semantic difference between them beyond the open flags that could be
> just passed to the open() call? Notably, Linux' getpt() is actually
> implemented as __posix_openpt (O_RDWR)...
We don't have an in-tree BSD port, and the BSD at the time was
probably quite different from what we have today. I suggest to ignore
the comment and rearrange things in the way that make the most sense
for Linux and Hurd.
next prev parent reply other threads:[~2019-12-31 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 21:35 posix_openpt vs getpt?? Samuel Thibault
2019-12-31 13:25 ` Florian Weimer [this message]
2019-12-31 16:38 ` Samuel Thibault
2019-12-31 16:45 ` Samuel Thibault
2019-12-31 16:53 ` Florian Weimer
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a778mxta.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=samuel.thibault@gnu.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).