Re: c++ code that egcs kills ...

["Glenn W. Bach" <glenn@dodgson.wonderland.caltech.edu>]

> Per Bothner said your code `is a fairly bogus and arcane (i.e.
> difficult-to-understand)'

> Joe Buck said `Leave the thunks in, and document the case that doesn't
> work.  It is very rare that it will arise in real code, and when it does
> it can be worked around. [...]

> Ulrich Drepper said `I agree with Joe.  I don't want to get in panic just
> because a well known but seldomly used feature does not work as
> expected'.

The reason we found this bug was that it hit us in "real" code. This was
not "bogus". The example code I sent was created to demonstrate in a simple
way what is happening in our code (which is not so simple). For us, this is
not a "seldomly used feature". It is at times the best way to solve a
problem, and is often unavoidable.

In a large loosly-coupled system like ours it becomes increasingly hard to
avoid this situation as the system grows.

p.s. Is there any way we can get around it by just recompiling *our* code?
Telling all of our users that they need to replace all of their libraries
is not going to work.

Glenn