This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: [RFC] Libstdc++ dll conformance solution. [Re: Cygwin 1.7 release (was Re: ??? The library or libraries will be delivered[...])]
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: cygwin-developers at cygwin dot com
- Date: Thu, 04 Jun 2009 15:16:32 +0100
- Subject: Re: [RFC] Libstdc++ dll conformance solution. [Re: Cygwin 1.7 release (was Re: ??? The library or libraries will be delivered[...])]
- References: <1244061552.9556.1318646127@webmail.messagingengine.com> <20090604091627.GS23519@calimero.vinschen.de> <4A27A9EB.6040400@gmail.com> <4A27B36E.1090700@gmail.com> <20090604130248.GA32087@calimero.vinschen.de>
Corinna Vinschen wrote:
>
> I would love to say yes, but this is somewhat beyond my expertise.
> Can you give an executive (for dummies) summary what would have to be
> changed in Cygwin and how this breaks backward compatibility with...
> anything?
Okeydokey. Now, where did I leave that sack of unused bullet points?
It'll take me a little while but I'll post a check-list style rundown of the
changes I'd want to add to the DLL followed by a number of worked examples of
use cases. I believe I can do it without breaking any back compat at all (but
without relinking, existing executables wont be able to benefit from the new
behaviour).
cheers,
DaveK