From: Mark Mitchell <mark@codesourcery.com>
To: Lubos Lunak <l.lunak@sh.cvut.cz>,
"kde-core-devel@mail.kde.org" <kde-core-devel@mail.kde.org>
Cc: Joe Buck <jbuck@synopsys.com>,
Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: KDE hackers, please read (was [nathan@codesourcery.com: Re: GCC 3.0.3: Bugs to Fix]) (fwd)
Date: Mon, 10 Dec 2001 09:55:00 -0000 [thread overview]
Message-ID: <21890000.1008006011@gandalf.codesourcery.com> (raw)
In-Reply-To: <200112101041.LAA06063@stoupa.sh.cvut.cz>
> 3) Persuade gcc folks to add compiler switch that makes gcc use string
> comparing when doing rtti, and simply compile whole KDE with this switch
> turned on.
All code in the application -- including the C++ run-time library --
needs to be compiled the same way, so you would have to rebuild
everything to do this.
In general, I will argue against any such change.
Mixing C++ and dlopen w/o RTLD_GLOBAL is fundamentally wrong.
The right model is that this is like using an uninitialized
variable. It might work somtimes, but it is a completely horrible
thing to do, totally unportable, and will succeed or fail based on
minor changes elsewhere in the code.
It would be a disservice for us to add features that try to accomodate
this; they cannot be made to work reliably and so all they would do
is create a temptation for people to write code that will not work.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2001-12-10 17:47 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 ` 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 [this message]
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
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=21890000.1008006011@gandalf.codesourcery.com \
--to=mark@codesourcery.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.com \
--cc=kde-core-devel@mail.kde.org \
--cc=l.lunak@sh.cvut.cz \
/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).