From: Oskar Enoksson <osken393@student.liu.se>
To: egcs@cygnus.com
Subject: Re: explicit specialization in non-namespace scope
Date: Mon, 21 Sep 1998 07:32:00 -0000 [thread overview]
Message-ID: <Pine.GSO.3.96.980921144445.7109I-100000@lystra.lysator.liu.se> (raw)
>>>>> "Nathan" == Nathan Myers <ncm@nospam.cantrip.org> writes:
>> I believe this is incorrect. I find no such restriction.
>> In addition, in 14.7.3 - Explicit specialization
>> [temp.expl.spec] we have:
>> -17- A member or a member template may be nested within
>> many enclosing class templates. If the declaration of an
>> explicit specialization for such a member appears in
>> namespace scope, the member declaration shall be preceded
>> by a template<> for each enclosing class template that is
>> explicitly specialized.
>>
>> It would not be necessary to say "if" above if that were
>> the only place it could appear.
>
>Since I implemented this, I'd better defend myself. :-)
>
> [temp.expl.spec]
>
> An explicit specialization shall be declared in the namespace of
> which the template is a member, or, for member templates, in the
> namespace of which the enclosing class or enclosing class
> template is a member. An explicit specialization of a member
> function, member class or static data member of a class template
> shall be declared in the namespace of which the class template
> is a member. */
Thanks for all answers!
I can also report that Digital cxx rejects explicit member template
specializations.
To bad, it was very useful ...
/Oskar
next reply other threads:[~1998-09-21 7:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-21 7:32 Oskar Enoksson [this message]
[not found] <Pine.GSO.3.96.980921144445.7109I-100000.cygnus.egcs@lystra.lysator.liu.se>
1998-09-21 19:37 ` Nathan Myers
1998-09-22 6:35 ` Alexandre Oliva
1998-09-22 9:00 ` Mark Mitchell
[not found] ` <199809220757.AAA30938.cygnus.egcs@smtp.earthlink.net>
1998-09-22 19:59 ` Nathan Myers
1998-09-23 8:43 ` Matthias Mueller
1998-09-28 16:32 ` Mark Mitchell
[not found] ` <199809282301.QAA19439.cygnus.egcs@smtp.earthlink.net>
1998-09-29 14:32 ` Nathan Myers
[not found] ` <org1dk8m82.fsf.cygnus.egcs@araguaia.dcc.unicamp.br>
1998-09-22 19:41 ` Nathan Myers
-- strict thread matches above, loose matches on Subject: below --
1998-09-17 9:59 Oskar Enoksson
1998-09-17 11:14 ` Alexandre Oliva
[not found] ` <orvhmmk52m.fsf.cygnus.egcs@tiete.dcc.unicamp.br>
1998-09-18 22:10 ` Nathan Myers
1998-09-19 12:03 ` Mark Mitchell
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=Pine.GSO.3.96.980921144445.7109I-100000@lystra.lysator.liu.se \
--to=osken393@student.liu.se \
--cc=egcs@cygnus.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).