Date:	Fri, 23 Nov 2001 10:04:15 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	tim DOT van DOT holder AT pandora DOT be
Message-Id:	<2593-Fri23Nov2001100415+0200-eliz@is.elta.co.il>
X-Mailer:	emacs 21.1.50 (via feedmail 8 I) and Blat ver 1.8.9
CC:	djgpp-workers AT delorie DOT com, pavenis AT lanet DOT lv
In-reply-to:	<000001c173b4$6052a120$fdf8e0d5@pandora.be>
	(tim DOT van DOT holder AT pandora DOT be)
Subject:	Re: GCC option -ansi and libstdc++-v3
References:	<000001c173b4$6052a120$fdf8e0d5 AT pandora DOT be>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
> Date: Fri, 23 Nov 2001 01:18:28 +0100
> 
> If using -ansi breaks, say,
> valarray (which is ANSI C++ IIRC) because one of the template functions
> uses a non-ANSI function, that is a problem.

Is this really the case?  How can ANSI C++ do that without polluting
the namespace?

Anyway, if that's the problem, we should solve it like we do with all
non-ANSI functions that are required by ANSI functions: rename the
real function to have two leading underscores, and make a stub for the
old name.  Then #define the old name somewhere (in _G_config.h?) so
that C++ headers are happy.

- Raw text -