delorie.com/archives/browse.cgi | search |
Date: | Tue, 13 Feb 2001 09:26:04 +0200 (IST) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | Laurynas Biveinis <lauras AT softhome DOT net> |
cc: | djgpp-workers AT delorie DOT com |
Subject: | Re: namespace std and libstdc++ V3 |
In-Reply-To: | <20010212204049.1165.qmail@lauras.lt> |
Message-ID: | <Pine.SUN.3.91.1010213092537.25782J-100000@is> |
MIME-Version: | 1.0 |
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 |
On Mon, 12 Feb 2001, Laurynas Biveinis wrote: > There are three C header strategies implemented in libstdc++-v3: > 1) c. This one does nothing - it leaves headers as is, like in V2. > 2) c_std. This one is default for now. It includes C headers in > global namespace and pulls standard functions into std namespace. > 3) c_shadow. This is WIP and is intended to become default in future. > And this is the one Stephen was talking about - namespace _C_legacy, > etc. Are you talking about the <*.h> headers or the <c*> headers? I understand that Stephen was working on allowing C++ programs to include the <*.h> headers.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |