General search for symbols...

[Zack Weinberg]

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>