va_list used in <stdio.h>

[Norman Diamond]

In article <13574 at bloom-beacon.MIT.EDU> scs at adam.pika.mit.edu (Steve Summit) writes:

>I realize that picking the right header file granularity involves
>tradeoffs.  There are probably programmers who dislike having to
>#include everything under the sun and would prefer an opposite
>extreme, something along the lines of <libc.h> or <everything.h>.
>Many of my source files start out with 15 or 20 #include
>directives, and while this may not be ideal, I much prefer the
>flexibility that finer granularity affords.

As a quality-of-implementation issue, both needs could be met.
<stdlib.h> can just be a list of nested #include's of standard (well,
not really standard, but what else do you call them) include files
with a finer grain.  (At least namespace pollution is not a problem
in naming standard include files.)

--
-- 
Norman Diamond, Sony Computer Science Lab (diamond%csl.sony.jp at relay.cs.net)
  The above opinions are inherited by your machine's init process (pid 1),
  after being disowned and orphaned.  However, if you see this at Waterloo or
  Anterior, then their administrators must have approved of these opinions.