public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: nathan@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/1611
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <20010116094600.18180.qmail@sourceware.cygnus.com> (raw)

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

From: nathan@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, nathan@gcc.gnu.org, nobody@gcc.gnu.org,
  snyder@fnal.gov
Cc:  
Subject: Re: c++/1611
Date: 16 Jan 2001 09:38:09 -0000

 Synopsis: c++ new-abi generates bad code with virtual derivation
 
 Responsible-Changed-From-To: unassigned->nathan
 Responsible-Changed-By: nathan
 Responsible-Changed-When: Tue Jan 16 01:38:09 2001
 Responsible-Changed-Why:
     patch in progress
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1611&database=gcc
>From bkoz@redhat.com Sun Apr 01 00:00:00 2001
From: Benjamin Kosnik <bkoz@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/2189: g++ rejects legal code
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010306015600.9588.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg02035.html
Content-length: 496

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

From: Benjamin Kosnik <bkoz@redhat.com>
To: gcc-bugs@gcc.gnu.org, mayer@tux.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/2189: g++ rejects legal code
Date: Mon, 5 Mar 2001 17:50:18 -0800

 For maximum clarity, default arguments always go with the
 declaration, not the definition.  See 8.3.6 Default arguments.
 
 Sadly though, your code is actually legal, just a bit confusing to
 read. This is a bug.
 
 -benjamin


             reply	other threads:[~2001-04-01  0:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-01  0:00 nathan [this message]
2001-04-01  0:00 c++/1611 nathan
2001-04-01  0:00 c++/1611 nathan

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=20010116094600.18180.qmail@sourceware.cygnus.com \
    --to=nathan@gcc.gnu.org \
    --cc=gcc-prs@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).