public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* re: An odd behavior of dynamic_cast
       [not found] <a71bd89a0512200809n2a0330fdx8299bb48c9fdee00@mail.gmail.com>
@ 2005-12-22 14:39 ` Shin-ichi MORITA
  0 siblings, 0 replies; only message in thread
From: Shin-ichi MORITA @ 2005-12-22 14:39 UTC (permalink / raw)
  To: Dan Kegel, gcc-help; +Cc: gcc

Hi Dan,

> I think the right place for this question might have
> been gcc-help (http://gcc.gnu.org/ml/gcc-help/).

Thanks to Ben, I've already posted the same question to
gcc-help.

> > [ Why doesn't dynamic_cast work when I dlopen a
> shared library? ]

I've checked out http://gcc.gnu.org/faq.html#dso.
But in fact, I'm writing python extention module,
so I can't call dlopen() with RTLD_GLOBAL flag.

My actual question is:
- Why dynamic_cast across shared libraries
  works for VirtualTag in test1?
  (though I use dlopen() in test1.)
- Is it correct to use this workaround
  (i.e. making a class polymorphic)
  when I can't use RTLD_GLOBAL flag?

Thanks.


--- Dan Kegel <dank@kegel.com> wrote:
> shin1_morita@yahoo.co.jp wrote:
> > [ Why doesn't dynamic_cast work when I dlopen a
> shared library? ]
> 
> I think the right place for this question might have
> been
> gcc-help (http://gcc.gnu.org/ml/gcc-help/).
> Nevertheless, I think
> http://gcc.gnu.org/faq.html#dso
> should answer your question.
> - Dan
> 
> --
> Wine for Windows ISVs: http://kegel.com/wine/isv


--------------------------------------
STOP HIV/AIDS.
Yahoo! JAPAN Redribbon Campaign 2005
http://pr.mail.yahoo.co.jp/redribbon/

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2005-12-22 14:39 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <a71bd89a0512200809n2a0330fdx8299bb48c9fdee00@mail.gmail.com>
2005-12-22 14:39 ` An odd behavior of dynamic_cast Shin-ichi MORITA

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).