public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Marc Espie <espie@quatramaran.ens.fr>
To: egcs-bugs@cygnus.com
Subject: semantics of C++ casts
Date: Fri, 20 Nov 1998 17:31:00 -0000	[thread overview]
Message-ID: <199811202333.AAA01041@quatramaran.ens.fr> (raw)
In-Reply-To: <Pine.GSO.3.95k.981120175851.12070A-100000@hegel>

In article < Pine.GSO.3.95k.981120175851.12070A-100000@hegel > you write:
>It's not a different class per se, it's a derived class.  Also, the code
>works on CC (SUN's) 4.2 as well as Portland Groups compiler.

Yes, so ?
Just because it happens to work on a different compiler doesn't mean it's
standard nor should be supported. reinterpret_cast<> and vtables -> anything
goes. 

Do you have a longer fragment that would show why you need to use 
reinterpret_cast ?  From what you've posted, it just looks like you're 
cutting corners by not calling dynamic_cast<> where you should, and that
Sun's CC is letting you off awfully easy.


      parent reply	other threads:[~1998-11-20 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-19 23:26 bug report Michael Lee
1998-11-20 14:08 ` Alexandre Oliva
1998-11-20 14:42 ` Martin von Loewis
1998-11-20 15:07   ` Michael Lee
1998-11-20 15:28     ` Martin von Loewis
1998-11-20 17:31     ` Marc Espie [this message]

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=199811202333.AAA01041@quatramaran.ens.fr \
    --to=espie@quatramaran.ens.fr \
    --cc=egcs-bugs@cygnus.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).