Re: The prototyping patch for rtl.h/rtl.def

[meissner@cygnus.com <meissner@cygnus.com>]

| Is it really safe to use #ifdef BUFSIZE?  What's to stop stdio.h from
| doing somethign like
| 
| const int BUFSIZE = 1024
| 
| ie, is there anything in ANSI that sez BUFSIZE must be a macro?

Yes, it is explicitly required to be a macro.  Quoting from a draft of C9X,
since I don't have the standard online:

       C9X Draft 10, 1997-06-27, WG14/Nxxx J11/97-xxx

       7.12  Input/output <stdio.h>

       7.12.1  Introduction

       [#1] The header  <stdio.h>  declares  three  types,  several
       macros, and many functions for performing input and output.

       [#2] The types declared are size_t (described in 7.1.6);

               FILE

       which is an object type other than an array type capable  of  |
       recording  all  the  information needed to control a stream,
       including its file position  indicator,  a  pointer  to  its
       associated  buffer (if any), an error indicator that records
       whether a read/write error has occurred, and an  end-of-file
       indicator  that records whether the end of the file has been
       reached; and

               fpos_t

       which is  an  object  type  capable  of  recording  all  the
       information needed to specify uniquely every position within
       a file.

       [#3] The macros are NULL (described in 7.1.6);

               _IOFBF
               _IOLBF
               _IONBF

       which expand to integral constant expressions with  distinct
       values,  suitable  for  use  as  the  third  argument to the
       setvbuf function;

               BUFSIZ

       which expands to an integral constant expression,  which  is
       the size of the buffer used by the setbuf function;