From: "John A. Tamplin" <jat@traveller.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: egcs@cygnus.com
Subject: Re: Implications of tighter integration of libg++
Date: Tue, 10 Feb 1998 00:53:00 -0000 [thread overview]
Message-ID: <Pine.A32.3.91.980210024926.19888N-100000@cyclone.traveller.com> (raw)
In-Reply-To: <199802092347.PAA19098@atrus.synopsys.com>
On Mon, 9 Feb 1998, Joe Buck wrote:
> Even so, perhaps a backward compatibility layer could be written. But it
> might be easier just to ship two libstdc++ versions with different major
> version numbers than to try to figure out how to make one library do. The
> whole reason for using the std namespace is so that users are freed up to
> use the hundreds of names the standard library takes away. Any scheme
> that tries to preserve backward compatibility will also pollute the
> namespace (preventing users from using certain identifier names), meaning
> that we won't have a conforming compiler.
Why couldn't you just have the compatibility layer in a separate library?
That way those symbols would only be used if it were explicitly added to
the link command. For those sites that didn't care about using the
previously reserved symbols, it could be automatically linked or even be
included as a separate object in the standard library.
John Tamplin Traveller Information Services
jat@Traveller.COM 2104 West Ferry Way
205/883-4233x7007 Huntsville, AL 35801
next prev parent reply other threads:[~1998-02-10 0:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-24 23:19 Loren J. Rittle
1997-11-25 6:52 ` Manfred.Hollstein
1998-02-09 2:22 ` Jeffrey A Law
1998-02-09 7:13 ` Martin von Loewis
1998-02-09 14:46 ` Joe Buck
1998-02-09 15:33 ` Martin von Loewis
1998-02-09 21:34 ` H.J. Lu
1998-02-09 21:34 ` Joe Buck
1998-02-10 0:53 ` John A. Tamplin [this message]
1998-02-10 10:30 ` Joe Buck
1998-02-09 11:54 ` Joe Buck
1998-02-09 14:46 ` H.J. Lu
[not found] ` <5837.887019874.cygnus.egcs@hurl.cygnus.com>
1998-02-09 11:31 ` Jason Merrill
1998-02-09 11:54 ` Jeffrey A Law
1998-02-09 11:54 ` Jason Merrill
1998-02-09 15:33 ` Fred Fish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.A32.3.91.980210024926.19888N-100000@cyclone.traveller.com \
--to=jat@traveller.com \
--cc=egcs@cygnus.com \
--cc=jbuck@synopsys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).