Thanks to those mentioned below for shedding light on the issue.

-------------------------------------------------------------------------------
Date: Mon, 5 Oct 92 09:56:55 PDT
From: jss%summit@lucid.com (Jerry Schwarz)

...

[The 15 filenames that follow are from the ANSI standard for C]

|> <assert.h>
|> <ctype.h>
|> <errno.h>
|> <float.h>
|> <limits.h>
|> <locale.h>
|> <math.h>
|> <setjmp.h>
|> <signal.h>
|> <stdarg.h>
|> <stddef.h>
|> <stdio.h>
|> <stdlib.h>
|> <string.h>
|> <time.h>

x3j16/wg21 has accepted the C library essentially as is.

|>
|> <complex.h>
|> <fstream.h>
|> <iostream.h>
|> <new.h>
|> <stream.h>               <-- obsolescent, of course
|> <strstream.h>
|>

new.h will be there (its already mentioned in the body of
the working paper)

iostream.h, fstream.h, strstream.h are under serious consideration
and will almost certainly be there, except that they may
be named "iostream", "fstream" and "strstream".  That is
there is some discussion of dropping the ".h".

complex.h will almost certainly not be there.
-------------------------------------------------------------------------------
From: jss%summit@lucid.com (Jerry Schwarz)

...

There were a bunch of nits that had to be changed.
        some stuff in setjmp/longjmp

        different approach to identifier reservation and linkage
        ... this is likely to change again

        wchar_t is a builtin primitive data type rather than a
        typedef.

        Description of exit changed,

        Some declarations were changed to be "const correct". E.g.
        strchr became overloaded.

                const char* strchr(const char*, int) ;
                char* strchr(char*,int) ;


        etc.

__STDC__ isn't a library issue.

-------------------------------------------------------------------------------
Steve Clamage, TauMetric Corp, steve@taumet.com
Vice Chair, ANSI C++ Committee, X3J16

...

Iostreams will be part of Standard C++, but not all the details have
been worked out.  I doubt that <stream.h> will be part of the Standard.

Complex has not so far been mentioned for inclusion in Standard.

There will probably be a string class and a bitset class in the Standard.

I think you can rely on individual implementations continuing to
provide the same headers and libraries they currently provide for
compatibility.
-------------------------------------------------------------------------------
--
John Davison
davisonj@ecn.purdue.edu