From mboxrd@z Thu Jan  1 00:00:00 1970
From: espie@quatramaran.ens.fr
To: mark@codesourcery.com
Cc: egcs@egcs.cygnus.com
Subject: Re: elided copy constructors
Date: Wed, 31 Mar 1999 23:46:00 -0000
Message-ID: <19990320142609.15873.qmail@quatramaran.ens.fr>
References: <36F2CDC1.8B4FEC4A@netwood.net> <199903192313.AAA00798@mira.isdn.cs.tu-berlin.de> <199903192356.PAA03038@adsl-206-170-148-33.dsl.pacbell.net>
X-SW-Source: 1999-03n/msg00693.html
Message-ID: <19990331234600.5uPllDEh2dLN3mWcy2Vjkp0BCny0-et9mQniUT-76Xw@z>

In article < 199903192356.PAA03038@adsl-206-170-148-33.dsl.pacbell.net > you write:

>  o Fix it yourself.  This alternative is guaranteed to bring results,
>    if you work hard enough, but will probably take a lot of time,
>    and, depending on the quality of your work and the perceived
>    benefits of your changes, your code may or may not ever make it
>    into an official release of EGCS.

This is false, plain and simple.

This alternative is NOT guaranteed to bring results. You may just be stupid
enough that you won't be able to fix it, or you may have stumbled into such
an horrid bug that extensive surgery to the whole compiler may be necessary,
in which case approach two is the only one that will work.

Stating that, with hard work, anyone is able to fix anything, is just
political correctness at its worst.

(and, to be more precise about this: we all have limitations. I know 
I do have limitations, which have nothing to do with time and hard work... 
there is stuff I can do, and there is stuff I never will be able to)