From: Zack Weinberg <zack@codesourcery.com>
To: Mike Stump <mrs@apple.com>
Cc: Joe Buck <jbuck@synopsys.com>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: General search for symbols...
Date: Thu, 10 Apr 2003 20:03:00 -0000 [thread overview]
Message-ID: <87he96tb0c.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <61A218EB-6B82-11D7-8AD9-003065A77310@apple.com>
Mike Stump <mrs@apple.com> writes:
> Ok, I am confused then. What does the varargs.h header in 3.3 do then:
>
> #ifndef _VARARGS_H
> #define _VARARGS_H
>
> #error "GCC no longer implements <varargs.h>."
> #error "Revise your code to use <stdarg.h>."
>
> #endif
This would be what we call "jumping to conclusions based on the
existence of the file."
What do you think of this revision? I'm not entirely happy with the
wording.
zw
===================================================================
Index: gcc-3.3/changes.html
--- gcc-3.3/changes.html 21 Mar 2003 09:01:04 -0000 1.22
+++ gcc-3.3/changes.html 10 Apr 2003 19:20:25 -0000
@@ -53,7 +53,10 @@
<li>The <code>-traditional</code> C compiler option has been
removed. It was deprecated in 3.1 and 3.2. (Traditional
- preprocessing remains available.)</li>
+ preprocessing remains available.) The
+ <code><varargs.h></code> header, used for writing
+ variadic functions in traditional C, still exists but will
+ produce an error message if used.</li>
</ul>
===================================================================
Index: gcc-3.4/changes.html
--- gcc-3.4/changes.html 10 Apr 2003 05:33:54 -0000 1.19
+++ gcc-3.4/changes.html 10 Apr 2003 19:20:25 -0000
@@ -22,11 +22,8 @@
<li>GCC no longer accepts the options <code>-fvolatile</code>,
<code>-fvolatile-global</code> and <code>-fvolatile-static</code>.
It is unlikely that they worked correctly in any 3.x release.</li>
- <li>GCC no longer supports the use of <code><varargs.h></code>
- and does not provide this header with the distribution. Use
- <code><stdarg.h></code> instead. (This header is primarily
- useful with traditional mode compilation, which feature was removed
- in GCC 3.3.)
+ <li>GCC no longer ships <code><varargs.h></code>. Use
+ <code><stdarg.h></code> instead.</li>
</ul>
<h2>General Optimizer Improvements</h2>
next prev parent reply other threads:[~2003-04-10 19:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 14:10 Stephen Biggs
2003-04-02 16:22 ` Hans-Peter Nilsson
2003-04-03 7:18 ` Stephen Biggs
2003-04-04 2:13 ` Hans-Peter Nilsson
2003-04-04 9:35 ` Zack Weinberg
2003-04-04 18:51 ` Joe Buck
2003-04-10 9:37 ` Zack Weinberg
2003-04-10 19:36 ` Mike Stump
2003-04-10 20:03 ` Zack Weinberg [this message]
2003-04-10 20:12 ` Mike Stump
2003-04-09 8:43 ` Stephen Biggs
2003-04-02 15:07 Ilia Dyatchkov
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=87he96tb0c.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.com \
--cc=mrs@apple.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.
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).