From: Joe Buck <jbuck@synopsys.COM>
To: mark@codesourcery.com (Mark Mitchell)
Cc: jbuck@synopsys.COM (Joe Buck), l.lunak@sh.cvut.cz (Lubos Lunak),
kde-core-devel@mail.kde.org (kde-core-devel@mail.kde.org),
Franz.Sirl-kernel@lauterbach.com (Franz Sirl),
gcc@gcc.gnu.org (gcc@gcc.gnu.org)
Subject: Re: KDE hackers, please read (was [nathan@codesourcery.com: Re: GCC
Date: Mon, 10 Dec 2001 11:47:00 -0000 [thread overview]
Message-ID: <200112101944.LAA18386@atrus.synopsys.com> (raw)
In-Reply-To: <47830000.1008012745@gandalf.codesourcery.com> from "Mark Mitchell" at Dec 10, 2001 11:32:25 AM
> Yes, if you really, really know what you are doing and you are willing
> to write code that is unportable, or that does not make use of many
> language features, and you know the ABI, you may be able to get away
> with this.
>
> You are, however, playing with fire.
No kidding. Elaborate reference counting mechanisms to make sure we don't
delete code objects where we still have data objects whose vtables don't
point there, the quirks of five completely distinct dynamic linking
systems on different OSes, etc. On the other hand, I used g++ in 1990.
That was fire, man.
next prev parent reply other threads:[~2001-12-10 19:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.42.0112041339390.30216-110000@bochum.stuttgart.redhat.com>
2001-12-04 13:21 ` KDE hackers, please read (was [nathan@codesourcery.com: Re: GCC 3.0.3: Bugs to Fix]) (fwd) Waldo Bastian
2001-12-04 13:29 ` shaheed
2001-12-04 14:51 ` Joe Buck
2001-12-04 16:37 ` Dirk Mueller
2001-12-05 12:16 ` Mark Mitchell
2001-12-09 23:58 ` Waldo Bastian
2001-12-10 0:52 ` Simon Hausmann
2001-12-10 2:45 ` Lubos Lunak
2001-12-10 9:55 ` Mark Mitchell
2001-12-10 11:16 ` KDE hackers, please read (was [nathan@codesourcery.com: Re: GCC Joe Buck
2001-12-10 11:39 ` Mark Mitchell
2001-12-10 11:47 ` Joe Buck [this message]
2001-12-11 13:00 ` KDE hackers, please read (was [nathan@codesourcery.com: Re: GCC 3.0.3: Bugs to Fix]) (fwd) Alexandre Oliva
2001-12-11 9:28 ` Mark Mitchell
2001-12-10 1:33 ` Richard Henderson
2001-12-10 2:41 ` Andreas Schwab
2001-12-10 2:07 ` Nathan Sidwell
2001-12-10 3:01 ` Jakub Jelinek
2001-12-05 1:23 ` Nathan Sidwell
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=200112101944.LAA18386@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=gcc@gcc.gnu.org \
--cc=kde-core-devel@mail.kde.org \
--cc=l.lunak@sh.cvut.cz \
--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).