This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of CD1 status.

317. Instantiation vs. specialization of facets

Section: 26 [localization] Status: CD1 Submitter: Martin Sebor Opened: 2001-05-04 Last modified: 2016-02-10

Priority: Not Prioritized

View all other issues in [localization].

View all issues with CD1 status.


The localization section of the standard refers to specializations of the facet templates as instantiations even though the required facets are typically specialized rather than explicitly (or implicitly) instantiated. In the case of ctype<char> and ctype_byname<char> (and the wchar_t versions), these facets are actually required to be specialized. The terminology should be corrected to make it clear that the standard doesn't mandate explicit instantiation (the term specialization encompasses both explicit instantiations and specializations).

Proposed resolution:

In the following paragraphs, replace all occurrences of the word instantiation or instantiations with specialization or specializations, respectively:, p4, Table 52,, p2,, p3,, p5,, p10, 22.2.2, p2,, p1,, p1, p2 and p3,, p1,, p1, 22,2,5, p1, 22,2,6, p2,, p7, and Footnote 242.

And change the text in, p4 from

An implementation is required to provide those instantiations for facet templates identified as members of a category, and for those shown in Table 52:


An implementation is required to provide those specializations...

[Nathan will review these changes, and will look for places where explicit specialization is necessary.]


This is a simple matter of outdated language. The language to describe templates was clarified during the standardization process, but the wording in clause 22 was never updated to reflect that change.