public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <paolo.bonzini@polimi.it>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>, bonzini@gnu.org
Cc: gcc@gcc.gnu.org, mongryong@sympatico.ca
Subject: Re: Turning off C++ casting?
Date: Tue, 04 Mar 2003 16:29:00 -0000	[thread overview]
Message-ID: <200302201527.08390.paolo.bonzini@polimi.it> (raw)
In-Reply-To: <m3lm0bgli7.fsf@uniton.integrable-solutions.net>

> That is funny because you previously stated that you wanted to avoid
> the dyanmic_cast<>.  Now, you're telling me that you are going to do it
> anyway.  That is an *inconsistent* position.

The original poster wants to do the dynamic_cast only in debug versions, not 
release versions.  He asked for a flag to do so and it was pointed out that 
it is not feasible to implement it.

> All this has nothing to do with GCC.

Yes, it really belongs in gcc-help.

Paolo

  parent reply	other threads:[~2003-03-04 16:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 10:05 Paolo Bonzini
2003-02-20 10:19 ` Gabriel Dos Reis
2003-02-20 12:18   ` Paolo Bonzini
2003-02-20 12:21     ` Vladimir Merzliakov
2003-02-20 12:45       ` Paolo Bonzini
2003-02-20 18:00       ` Jack Lloyd
2003-02-20 12:28     ` Gabriel Dos Reis
2003-02-20 12:56       ` Paolo Bonzini
2003-02-20 13:22         ` Gabriel Dos Reis
2003-02-20 17:26           ` Mongryong
2003-03-04 16:29           ` Paolo Bonzini [this message]
     [not found] <B11C8538-4464-11D7-B22E-003065A77310@apple.com>
2003-02-20  0:24 ` Turning off C++ casting?? Mongryong
     [not found]   ` <20030219174232.A21518@synopsys.com>
2003-02-20  2:33     ` Mongryong
2003-02-20  9:54       ` Vladimir Merzliakov
  -- strict thread matches above, loose matches on Subject: below --
2003-02-19 23:15 Mongryong
2003-02-19 23:37 ` Jack Lloyd
2003-02-19 23:43   ` Mongryong

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=200302201527.08390.paolo.bonzini@polimi.it \
    --to=paolo.bonzini@polimi.it \
    --cc=bonzini@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=mongryong@sympatico.ca \
    /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).