public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matt Austern <austern@apple.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [Darwin] Patch c++/15428
Date: Mon, 24 May 2004 22:12:00 -0000	[thread overview]
Message-ID: <EC23C48E-ADB5-11D8-8286-000A95AA5E5E@apple.com> (raw)
In-Reply-To: <xyp7jv1d4w0.fsf@miranda.boston.redhat.com>

On May 24, 2004, at 12:03 PM, Jason Merrill wrote:

> The whole business about not setting the explicit bit is a kludge to 
> allow
> explicit instantiations of a class when not all of the members have 
> been
> defined.  It would probably be better to handle that directly in
> do_type_instantiation, and just always set the explicit bit.

I agree that that would  be cleaner.  It would also be consistent with
the direction that I think the standards committee is moving in.

I'll make sure that doesn't break the build (i.e. that nothing in 
libstdc++
or libjava depends on the old behavior), and, if it looks OK, I'll 
submit a
patch to make that change.

			--Matt

  reply	other threads:[~2004-05-24 19:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20  1:49 Matt Austern
2004-05-20 18:13 ` Jason Merrill
2004-05-20 20:28   ` Matt Austern
2004-05-20 21:02     ` Jason Merrill
2004-05-20 22:08       ` Matt Austern
2004-05-20 22:16         ` Jason Merrill
2004-05-22  8:54           ` Matt Austern
2004-05-22 12:25             ` Jason Merrill
2004-05-22 13:14               ` Matt Austern
2004-06-03 22:10             ` [Darwin] Patch c++/15428 (revised) Matt Austern
2004-06-03 22:43               ` Jason Merrill
2004-05-24 12:57           ` [Darwin] Patch c++/15428 Matt Austern
2004-05-24 21:57             ` Jason Merrill
2004-05-24 22:12               ` Matt Austern [this message]
2004-05-25  2:29                 ` Matt Austern
2004-05-25 21:43                   ` Jason Merrill
2004-05-25  2:40 Benjamin Kosnik

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=EC23C48E-ADB5-11D8-8286-000A95AA5E5E@apple.com \
    --to=austern@apple.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.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).