public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	martin@loewis.home.cs.tu-berlin.de, nobody@gcc.gnu.org,
	paul.thomas@eds.com
Subject: Re: c++/50: problem calling destructor on typedef of int within namespace
Date: Tue, 31 Dec 2002 16:17:00 -0000	[thread overview]
Message-ID: <20030101001702.10932.qmail@sources.redhat.com> (raw)

Synopsis: problem calling destructor on typedef of int within namespace

State-Changed-From-To: suspended->closed
State-Changed-By: neil
State-Changed-When: Tue Dec 31 16:17:01 2002
State-Changed-Why:
    Fixed for 3.4.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=50


             reply	other threads:[~2003-01-01  0:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31 16:17 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-01 18:46 Christian Ehrhardt
2001-11-16 12:56 nathan
2001-11-16 11:06 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=20030101001702.10932.qmail@sources.redhat.com \
    --to=neil@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=martin@loewis.home.cs.tu-berlin.de \
    --cc=nobody@gcc.gnu.org \
    --cc=paul.thomas@eds.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).