This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: PR3042
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Subject: Re: PR3042
- From: Jason Merrill <jason_merrill at redhat dot com>
- Date: 11 Jun 2001 20:34:01 +0100
- Cc: Mark Mitchell <mark at codesourcery dot com>, Phil Edwards <pedwards at disaster dot jaj dot com>, "dje at watson dot ibm dot com" <dje at watson dot ibm dot com>, "Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr" <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>, "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>
- References: <Pine.SOL.3.91.1010611110746.26841A@taarna.cygnus.com>
>>>>> "Benjamin" == Benjamin Kosnik <bkoz@redhat.com> writes:
> This is my last response to this thread.
>> You mean, they don't use static data member templates?
> That is my understanding. Perhaps I'm off.
I have no idea.
>> I don't see how you can consider the 2.95 semantics "broken". They are
>> more conformant than Mark's proposal, in that more valid code can be
>> compiled. The question is, how common is code which is accepted under the
>> status quo that would not be accepted under Mark's proposal? Is it common
>> enough to justify the extra complexity in the compiler and for users?
> v3 uses a lot of const static data members, and static data members, so
> it's common enough for me.
Yes, but v3 is an instance of valid code which is not accepted under the
status quo. I'm wondering if there are any significant bodies of code that
would work under the status quo and would not under Mark's proposal.
Jason