Title
Proposition: Clarification of the interaction between a facet and an iterator
Status
nad
Section
[locale.category]
Submitter
Christopher Conrade Zseleghovski

Created on 2005-06-07.00:00:00 last changed 172 months ago

Messages

Date: 2010-10-21.18:28:33

[ 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. ]

Date: 2010-10-21.18:28:33

Proposed resolution:

Append the following point to 22.1.1.1.1:

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.

Date: 2010-10-21.18:28:33

[ 2009-07 Frankfurt ]

No objection to NAD, Fixed.

Move to NAD.

Date: 2005-06-07.00:00:00

Motivation:

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.

History
Date User Action Args
2010-10-21 18:28:33adminsetmessages: + msg2865
2010-10-21 18:28:33adminsetmessages: + msg2864
2010-10-21 18:28:33adminsetmessages: + msg2863
2005-06-07 00:00:00admincreate