public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mtk.manpages at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug manual/17011] Example in "Allocating Pseudo-Terminals" section uses isastream
Date: Mon, 02 Jun 2014 14:00:00 -0000 [thread overview]
Message-ID: <bug-17011-131-JZ97UzL7H9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17011-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17011
--- Comment #2 from Michael Kerrisk <mtk.manpages at gmail dot com> ---
(In reply to Andreas Schwab from comment #1)
> isastream is declared in <stropts.h>.
But that misses the point. The isastream() implementation is a placeholder that
does nothing much useful. The example code really shouldn't be using
isastream(); that piece of the code is System-Vish, and rather irrelevant these
days.
There are other pieces of that section of the glibc manual that are also rather
crufty. For example, no-one should use the GNU getpt() these days. Use
posix_openpt() instead.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-06-02 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 12:23 [Bug manual/17011] New: " GavinSmith0123 at gmail dot com
2014-06-02 13:15 ` [Bug manual/17011] " schwab@linux-m68k.org
2014-06-02 14:00 ` mtk.manpages at gmail dot com [this message]
2014-06-02 14:13 ` schwab@linux-m68k.org
2014-06-02 14:21 ` mtk.manpages at gmail dot com
2014-06-12 19:09 ` fweimer at redhat dot com
2015-06-07 16:24 ` GavinSmith0123 at gmail dot com
2023-04-11 11:34 ` GavinSmith0123 at gmail dot com
2023-04-11 11:42 ` GavinSmith0123 at gmail dot com
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=bug-17011-131-JZ97UzL7H9@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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).