diff options
author | Rich Felker <dalias@aerifal.cx> | 2013-04-08 23:09:11 -0400 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2013-04-08 23:09:11 -0400 |
commit | 23ab8c255543a7e0876c7e1858ef0d4bbd562729 (patch) | |
tree | b39700bf54a23ae14a94436e2c5cb80134373f35 /src/math/exp2.c | |
parent | ea34b1b90ca5ba3b87725662f6a1ff03b7a88a1f (diff) | |
download | musl-23ab8c255543a7e0876c7e1858ef0d4bbd562729.tar.gz musl-23ab8c255543a7e0876c7e1858ef0d4bbd562729.tar.xz musl-23ab8c255543a7e0876c7e1858ef0d4bbd562729.zip |
mbrtowc: do not leave mbstate_t in permanent-fail state after EILSEQ
the standard is clear that the old behavior is conforming: "In this case, [EILSEQ] shall be stored in errno and the conversion state is undefined." however, the specification of mbrtowc has one peculiarity when the source argument is a null pointer: in this case, it's required to behave as mbrtowc(NULL, "", 1, ps). no motivation is provided for this requirement, but the natural one that comes to mind is that the intent is to reset the mbstate_t object. for stateful encodings, such behavior is actually specified: "If the corresponding wide character is the null wide character, the resulting state described shall be the initial conversion state." but in the case of UTF-8 where the mbstate_t object contains a partially-decoded character rather than a shift state, a subsequent '\0' byte indicates that the previous partial character is incomplete and thus an illegal sequence. naturally, applications using their own mbstate_t object should clear it themselves after an error, but the standard presently provides no way to clear the builtin mbstate_t object used when the ps argument is a null pointer. I suspect this issue may be addressed in the future by specifying that a null source argument resets the state, as this seems to have been the intent all along. for what it's worth, this change also slightly reduces code size.
Diffstat (limited to 'src/math/exp2.c')
0 files changed, 0 insertions, 0 deletions