Go to file
Benjamin Kosnik 9ece379a8a Shadow headers would work if libsupc++ was strict about namespaces.
2000-10-16  Benjamin Kosnik  <bkoz@gnu.org>

	Shadow headers would work if libsupc++ was strict about namespaces.
	This only possible if g++ maps std::size_t -> size_t. (Hint hint.)
	* include/c_std/assert.h: Add guards.
	* include/c_std/bits/std_climits.h: Correct typo.
	* include/c_std/ctype.h: Remove #error.

	* libio/libioP.h: Break up extern "C" bits around includes.
	* libio/libio.h: Only include C headers, or else _C_legacy namespaces
	will be nested.
	* libio/libioP.h: Same here.

From-SVN: r36900
2000-10-17 08:25:08 +00:00
boehm-gc
config
contrib * gperf-2.7-19981006.pat: Remove. 2000-10-14 10:56:48 +01:00
etc
gcc Daily bump. 2000-10-17 01:45:08 -06:00
include
INSTALL
libchill
libf2c Daily bump. 2000-10-17 01:45:08 -06:00
libffi
libiberty
libio iostream.cc (ostream::operator<<(double n)): Initialize new fields wide and i18n of struct printf_info. 2000-10-16 09:41:01 +02:00
libjava exception.cc: Don't #include "exception". 2000-10-13 05:45:57 +01:00
libobjc
libstdc++
libstdc++-v3 Shadow headers would work if libsupc++ was strict about namespaces. 2000-10-17 08:25:08 +00:00
texinfo
zlib configure.in (zlib_basedir): Cope with empty with_target_subdir 2000-10-10 11:01:30 +00:00
.cvsignore
ChangeLog Only create gcc/configargs.h if gcc build directory is present 2000-10-17 03:00:51 +00:00
config-ml.in
config.guess
config.if config.if: Search libstdc++-v3/configure.in for INTERFACE, when configured for libstdc++-v3. 2000-10-16 10:00:43 -06:00
config.sub
configure Only create gcc/configargs.h if gcc build directory is present 2000-10-17 03:00:51 +00:00
configure.in
COPYING
COPYING.LIB
djunpack.bat
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.in
missing
mkdep
mkinstalldirs
move-if-change
README
symlink-tree
ylwrap

		   README for GNU development tools

This directory contains various GNU compilers, assemblers, linkers, 
debuggers, etc., plus their support routines, definitions, and documentation.


Check the INSTALL directory for detailed configuration and installation
instructions.


Much of the code and documentation enclosed is copyright by
the Free Software Foundation, Inc.  See the file COPYING or
COPYING.LIB in the various directories, for a description of the
GNU General Public License terms under which you can copy the files.

REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
on where and how to report problems.