Title
"Noconv" definition too vague
Status
tc1
Section
[locale.codecvt]
Submitter
Nathan Myers

Created on 1998-08-06.00:00:00 last changed 163 months ago

Messages

Date: 2010-10-21.18:28:33

Proposed resolution:

Change the entry for noconv in the table under paragraph 4 in section [locale.codecvt.virtuals] to read:

noconv: internT and externT are the same type, and input sequence is identical to converted sequence.

Change the Note in paragraph 2 to normative text as follows:

If returns noconv, internT and externT are the same type and the converted sequence is identical to the input sequence [from,from_next). to_next is set equal to to, the value of state is unchanged, and there are no changes to the values in [to, to_limit).

Date: 1998-08-06.00:00:00

In the definitions of codecvt<>::do_out and do_in, they are specified to return noconv if "no conversion is needed". This definition is too vague, and does not say normatively what is done with the buffers.

History
Date User Action Args
2010-10-21 18:28:33adminsetmessages: + msg44
1998-08-06 00:00:00admincreate