From: espie@quatramaran.ens.fr
To: mark@codesourcery.com
Cc: egcs@egcs.cygnus.com
Subject: Re: elided copy constructors
Date: Sat, 20 Mar 1999 06:26:00 -0000 [thread overview]
Message-ID: <19990320142609.15873.qmail@quatramaran.ens.fr> (raw)
In-Reply-To: < 199903192356.PAA03038@adsl-206-170-148-33.dsl.pacbell.net >
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)
WARNING: multiple messages have this Message-ID
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 [thread overview]
Message-ID: <19990320142609.15873.qmail@quatramaran.ens.fr> (raw)
Message-ID: <19990331234600.5uPllDEh2dLN3mWcy2Vjkp0BCny0-et9mQniUT-76Xw@z> (raw)
In-Reply-To: <199903192356.PAA03038@adsl-206-170-148-33.dsl.pacbell.net>
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)
next prev parent reply other threads:[~1999-03-20 6:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-19 14:23 E. Robert Tisdale
[not found] ` < 36F2CDC1.8B4FEC4A@netwood.net >
1999-03-19 15:18 ` Martin v. Loewis
[not found] ` < 199903192313.AAA00798@mira.isdn.cs.tu-berlin.de >
1999-03-19 15:54 ` Mark Mitchell
[not found] ` < 199903192356.PAA03038@adsl-206-170-148-33.dsl.pacbell.net >
1999-03-19 19:20 ` Tim Hollebeek
1999-03-31 23:46 ` Tim Hollebeek
1999-03-20 6:26 ` espie [this message]
[not found] ` < 19990320142609.15873.qmail@quatramaran.ens.fr >
1999-03-20 7:18 ` Martin v. Loewis
[not found] ` < 199903201510.QAA08826@mira.isdn.cs.tu-berlin.de >
1999-03-20 9:50 ` Mark Mitchell
[not found] ` < 199903201752.JAA04517@adsl-206-170-148-33.dsl.pacbell.net >
1999-03-20 11:16 ` craig
1999-03-31 23:46 ` craig
1999-03-31 23:46 ` Mark Mitchell
1999-03-31 23:46 ` Martin v. Loewis
1999-03-31 23:46 ` espie
1999-03-21 6:09 ` Gerald Pfeifer
1999-03-28 9:45 ` Mark Mitchell
1999-03-29 12:50 ` Gerald Pfeifer
1999-03-31 23:46 ` Gerald Pfeifer
1999-03-31 23:46 ` Mark Mitchell
1999-03-31 23:46 ` Gerald Pfeifer
1999-03-21 8:41 ` New webpage? Providing egcs support Gerald Pfeifer
[not found] ` < Pine.GSO.4.10.9903211733410.1651-100000@markab.dbai.tuwien.ac.at >
1999-03-21 9:38 ` Mark Mitchell
1999-03-31 23:46 ` Mark Mitchell
1999-03-21 11:08 ` Jeffrey A Law
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Gerald Pfeifer
1999-03-31 23:46 ` elided copy constructors Mark Mitchell
1999-03-31 23:46 ` Martin v. Loewis
1999-03-31 23:46 ` E. Robert Tisdale
1999-03-19 15:37 Timmy Mulligins
1999-03-31 23:46 ` Timmy Mulligins
[not found] <36F2CDC1.8B4FEC4A.cygnus.egcs@netwood.net>
1999-03-20 1:12 ` Jason Merrill
1999-03-31 23:46 ` Jason Merrill
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=19990320142609.15873.qmail@quatramaran.ens.fr \
--to=espie@quatramaran.ens.fr \
--cc=egcs@egcs.cygnus.com \
--cc=mark@codesourcery.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).