[Bug c++/13294] [3.4 Regression] namespace associations vs. specializations

[jason at redhat dot com]

------- Additional Comments From jason at redhat dot com  2004-04-14 19:27 -------
Subject: Re:  [3.4 Regression] namespace associations vs.
 specializations

On 14 Apr 2004 18:27:14 -0000, "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org> wrote:

> Ahem.  With Jason's patch (not the recent), how serious is the
> remaining part of the problem?  (This is not a rhetorical question, I
> just want to hear of a nother evaluation). 
> Is the real problem the fact that the current mangling implementation
> does not take context into account?

No.  The real problem, as I see it now, is that we're trying to warp the
mangling implementation in order to make it easier to break code in subtle
and surprising ways, as you described in your message titled "ODR violation
made easy".  Which I regret not having responded to sooner.

  http://gcc.gnu.org/ml/libstdc++/2004-03/msg00016.html

I don't think supporting transparent interlinking of code compiled in
different modes is a good idea.  Requiring the debug and normal containers
to be ABI-compatible with one another would seem to restrict the checking
abilities of the debug containers quite a bit.  And if we don't require
that, any interlinking will cause horrible breakage.

The feature described in 13294 is intended to make this interlinking work
for specializations.  Given my skepticism about the usefulness of
interlinking in the first place, I don't think going out of our way to make
it work in more cases is appropriate.

Jason


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13294