public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9558: subclass cannot find parent members without explicit "this->" in some cases
Date: Tue, 04 Feb 2003 00:26:00 -0000	[thread overview]
Message-ID: <20030204002600.26517.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/9558; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: "Ryan C. Gordon" <ryan@epicgames.com>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/9558: subclass cannot find parent members without explicit
 "this->" in some cases
Date: Mon, 3 Feb 2003 18:21:52 -0600 (CST)

 > If that's how C++ works in the official spec, it's not how it works in 
 > real life.
 
 I think we all understand this, but this is just so because compilers 
 previously didn't implement the standard correctly and did not _force_ you 
 to write compliant code. Mark et al dared to do so in the new parser.
 
 
 > I've got half a million lines of code in Unreal Tournament 2003 that 
 > this "feature" breaks, which compile fine on everything from CodeWarrior 
 > to Intel's compiler to Visual C to GCC 2.95.3, 3.1, and 3.2. I can list 
 > at least five other games I've worked on that this breaks. I do not 
 > control or write this code, I just port it.
 
 gcc 2.95 ... 3.2 accept it, but just because they don't implement the 
 standard.
 
 Intel icc accepts it, unless for example you switch on -Xc -ansi. If you 
 do so, then it won't accept your code either. AFAIK, the same holds for 
 HP's aCC.
 
 The situation might be worse than you think: if two-stage name lookup is 
 not implemented, then you might get wrong results sometimes. So you have 
 to decide whether you implement the standard or the old status quo.
 
 
 > Surely there's got to be some consideration for backwards compatibility, 
 > if not real world issues?
 
 I think the answer will be: if you want to use a newer compiler, fix your 
 code. I fixed my 250k lines of code, which was painful admittedly, but I 
 think it's necessary.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-02-04  0:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04  0:26 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-04  2:46 Wolfgang Bangerth
2003-02-04  2:36 Ryan C. Gordon
2003-02-04  0:56 Wolfgang Bangerth
2003-02-03 23:45 bangerth
2003-02-03 23:36 ryan

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=20030204002600.26517.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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).