Title
do_unshift for codecvt<char, char, mbstate_t>
Status
cd1
Section
[locale.codecvt.virtuals]
Submitter
Thomas Plum

Created on 2007-04-16.00:00:00 last changed 164 months ago

Messages

Date: 2010-10-21.18:28:33

Proposed resolution:

Change [locale.codecvt.virtuals], p7:

Effects: Places characters starting at to that should be appended to terminate a sequence when the current stateT is given by state.237) Stores no more than (to_limit -to) destination elements, and leaves the to_next pointer pointing one beyond the last element successfully stored. codecvt<char, char, mbstate_t> stores no characters.

Date: 2007-04-16.00:00:00

[locale.codecvt.virtuals], para 7 says (regarding do_unshift):

Effects: Places characters starting at to that should be appended to terminate a sequence when the current stateT is given by state.237) Stores no more than (to_limit - to) destination elements, and leaves the to_next pointer pointing one beyond the last element successfully stored. codecvt<char, char, mbstate_t> stores no characters.

The following objection has been raised:

Since the C++ Standard permits a nontrivial conversion for the required instantiations of codecvt, it is overly restrictive to say that do_unshift must store no characters and return noconv.

[Plum ref _222152Y50]

History
Date User Action Args
2010-10-21 18:28:33adminsetmessages: + msg3368
2007-04-16 00:00:00admincreate