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++/9575: Internal compiler error in resolve_offset_ref, at cp/init.c:    1886
Date: Wed, 05 Feb 2003 00:16:00 -0000	[thread overview]
Message-ID: <20030205001600.21976.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Meenaradchagan Vishnu <mvishnu@fla.fujitsu.com>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/9575: Internal compiler error in resolve_offset_ref, at
 cp/init.c:    1886
Date: Tue, 4 Feb 2003 18:14:29 -0600 (CST)

 > Thank you very much for your prompt response.  Is the restriction on
 > paranthesis use conforms to the C++ standards?
 
 Yes.
 
 
 > Note that this code compiles and works as intended on other compilers.
 
 Right, but this is accidentally, or at best an extension of these 
 compilers. I think in prior versions of gcc this was more by chance.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-02-05  0:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05  0:16 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-05  0:06 Meenaradchagan Vishnu
2003-02-04 23:35 bangerth
2003-02-04 23:26 mvishnu

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