Created on 2021-09-12.00:00:00 last changed 12 months ago
Proposed resolution:
Change in 6.8.2 [basic.fundamental] paragraph 17 as follows:
The types described in this subclause are called fundamental types. The representation of a fundamental type is implementation-defined, subject to the constraints in this subclause.
CWG 2023-12-01
Since there is no requirement for "implementation-defined" in the specification, the representation is unspecified by omission. It was noted that "unspecified behavior" has well-defined (and narrow) meaning, whereas the not-specified property here is static throughout the instance of the abstract machine. In that sense, it is similar to implementation-defined, abent the documentation requirement. It might be worthwhile to have a defined term for such properties.
Proposed resolution [SUPERSEDED]:
Change in 6.8.2 [basic.fundamental] paragraph 17 as follows:
The types described in this subclause are called fundamental types. The representation of a fundamental type is unspecified except as stated in this subclause.
(From editorial issue 4893.)
It is unclear whether the representation of unsigned integral types is unspecified or implementation-defined.
History | |||
---|---|---|---|
Date | User | Action | Args |
2023-12-02 13:35:39 | admin | set | messages: + msg7536 |
2023-12-02 13:35:39 | admin | set | messages: + msg7535 |
2023-11-22 22:39:38 | admin | set | messages: + msg7521 |
2021-09-12 00:00:00 | admin | create |