This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of New status.
Section: 188.8.131.52 [ios.base.storage] Status: New Submitter: Jiang An Opened: 2022-02-14 Last modified: 2022-03-04
View all other issues in [ios.base.storage].
View all issues with New status.
Currently 184.108.40.206 [ios.base.storage] p5 and p8 say "On failure, a valid long&/void*& initialized to 0". Such wording seems wrong, because a long&/void*& variable or return value can't be initialized with 0. And the values of referenced objects may be underspecified, because an implementation may reuse the same long/void* objects on failure, and thus it's insufficient to specify the initial values of these objects only.
[2022-03-04; Reflector poll]
Set priority to 4 after reflector poll.
This wording is relative to N4901.
Modify 220.127.116.11 [ios.base.storage] as indicated:
long& iword(int idx);
-3- […]-4- […] -5- Returns: On success iarray[idx]. On failure, a
validlong & initialized to 0.void*& pword(int idx);
-6- […]-7- […] -8- Returns: On success parray[idx]. On failure a
validvoid* & initialized to 0. -9- Remarks: After a subsequent call to pword(int) for the same object, the earlier return value may no longer be valid.