This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 117b. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.
2025-08-11
2229. Volatile unnamed bit-fieldsSection: 11.4.10 [class.bit] Status: CD5 Submitter: David Majnemer Date: 2016-02-08[Accepted as a DR at the March, 2018 (Jacksonville) meeting.]
According to 11.4.10 [class.bit] paragraph 2, unnamed bit-fields are not members, but there does not appear to be a prohibition against their being declared volatile. Is this intended?
Proposed resolution (November, 2017)
Change 11.4.10 [class.bit] paragraph 2 as follows:
A declaration for a bit-field that omits the identifier declares an unnamed bit-field. Unnamed bit-fields are not members and cannot be initialized. An unnamed bit-field shall not be declared with a cv-qualified type. [Note: An unnamed bit-field is useful for padding...
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4