public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: shaheed <srhaque@iee.org>
To: kde-core-devel@mail.kde.org
Cc: gcc@gcc.gnu.org
Subject: Re: KDE hackers, please read (was [nathan@codesourcery.com: Re: GCC 3.0.3: Bugs to Fix]) (fwd)
Date: Tue, 04 Dec 2001 13:29:00 -0000	[thread overview]
Message-ID: <E16BN87-0000mX-00@carbon.btinternet.com> (raw)
In-Reply-To: <200112042117.fB4LHCl03492@linux.local>

Hi

> > If you want dynamic cast (and that's just one thing) to work with dlope
> > in gcc3+, you need to use RTLD_GLOBAL. (Don't get confused by Nathan no
> > understanding what if and only if means)

> That's pretty bad because loading (dlopen'ing) parts with RTLD_GLOBAL i
> asking for trouble. There is no way that we can guarantee that one par
> doesn't by chance use the same name for some class/symbols as another part
> since parts may get developed independently of each other

> We are already running into trouble with the flash plugin colliding wit
> OpenGL (both define "DisplayList") and things like this aren't helping th
> situation

> The alternative, banning RTTI from KDE, isn't very attractive either

Note that there is at least one use of RTTI in the MS Word import filter for 
KWord. It *could* be eliminated in favour of an alternative hack if required, 
but RTTI is needed at present at least

Thanks, Shahee

  reply	other threads:[~2001-12-04 21:29 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 [this message]
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
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=E16BN87-0000mX-00@carbon.btinternet.com \
    --to=srhaque@iee.org \
    --cc=gcc@gcc.gnu.org \
    --cc=kde-core-devel@mail.kde.org \
    /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).