From: Andreas Schwab <schwab@suse.de>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: Per Bothner <per@bothner.com>, <gcc@gcc.gnu.org>
Subject: Re: misleading statement in bugs.html#known
Date: Thu, 06 Dec 2001 04:46:00 -0000 [thread overview]
Message-ID: <jeher4bkdv.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.BSF.4.43.0112061238420.25049-100000@naos.dbai.tuwien.ac.at> (Gerald Pfeifer's message of "Thu, 6 Dec 2001 12:39:43 +0100 (CET)")
Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
|> On 5 Dec 2001, Andreas Schwab wrote:
|> >|> The point is that glibc allows you to *assign* to stdin, so it is
|> >|> no longer constant. This is a questionable feature..
|> > No. The real reason is that using the address of a static object is a
|> > nightmare in context of maintaining binary compatibility. Platforms that
|> > use copy relocations will lose if the size of the FILE type changes.
|>
|> Would (one of) you (who knows this stuff) mind updating bugs.html?
How about this:
--- bugs.html.~1.45.~ Sun Nov 4 00:14:32 2001
+++ bugs.html Thu Dec 6 13:29:35 2001
@@ -276,10 +276,10 @@
</code></blockquote>
will not compile with GNU libc (GNU/Linux libc6), because
-<code>stdin</code> is not a constant. This was done deliberately, in
-order for there to be no limit on the number of open <code>FILE</code>
-objects. It is surprising for people used to traditional Unix C
-libraries, but it is permitted by the C standard.</p>
+<code>stdin</code> is not a constant. This was done deliberately, to make
+it easier to maintain binary compatibility when the type <code>FILE</code>
+needs to be changed. It is surprising for people used to traditional Unix
+C libraries, but it is permitted by the C standard.</p>
<p>This construct commonly occurs in code generated by old versions of
lex or yacc. We suggest you try regenerating the parser with a
Andreas.
--
Andreas Schwab "And now for something
Andreas.Schwab@suse.de completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
next prev parent reply other threads:[~2001-12-06 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 13:16 Per Bothner
2001-12-05 13:52 ` Geoff Keating
2001-12-06 12:33 ` Per Bothner
2001-12-06 15:48 ` Richard Henderson
2001-12-05 14:38 ` Andreas Schwab
2001-12-06 4:31 ` Gerald Pfeifer
2001-12-06 4:46 ` Andreas Schwab [this message]
2001-12-06 7:18 ` Gerald Pfeifer
2001-12-06 7:35 ` Andreas Schwab
2001-12-06 10:08 ` Gerald Pfeifer
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=jeher4bkdv.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=per@bothner.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).