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

502. Proposition: Clarification of the interaction between a facet and an iterator

Section: [locale.category] Status: NAD Submitter: Christopher Conrade Zseleghovski Opened: 2005-06-07 Last modified: 2017-02-03

Priority: Not Prioritized

View all other issues in [locale.category].

View all issues with NAD status.



This requirement seems obvious to me, it is the essence of code modularity. I have complained to Mr. Plauger that the Dinkumware library does not observe this principle but he objected that this behaviour is not covered in the standard.

[ 2009-07 Frankfurt ]

No objection to NAD, Fixed.

Move to NAD.

Proposed resolution:

Append the following point to

6. The implementation of a facet of Table 52 parametrized with an InputIterator/OutputIterator should use that iterator only as character source/sink respectively. For a *_get facet, it means that the value received depends only on the sequence of input characters and not on how they are accessed. For a *_put facet, it means that the sequence of characters output depends only on the value to be formatted and not of how the characters are stored.

[ Berlin: Moved to Open, Need to clean up this area to make it clear locales don't have to contain open ended sets of facets. Jack, Howard, Bill. ]