Date: Wed, 6 Nov 2024 13:24:03 +0100
I'm reading the draft minutes from the last WG14 meeting
https://www.open-std.org/JTC1/sc22/wg14/www/docs/n3372.pdf
It seems some features were approved for the post-C23 version
of ISO C (called C2y) that should get liaison exposure.
For example:
Obsolete implicitly octal literals and add delimited escape sequences
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3353.htm
C++ proposal:
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0085r0.html
Allowing stricter alignment for atomic types
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3312.pdf
Case range expressions
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3370.htm
Named loops
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3355.htm
Other possibly interesting features:
Strong typedefs
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3320.htm
Tail recursion for preprocessor macros
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3307.htm
Jens
https://www.open-std.org/JTC1/sc22/wg14/www/docs/n3372.pdf
It seems some features were approved for the post-C23 version
of ISO C (called C2y) that should get liaison exposure.
For example:
Obsolete implicitly octal literals and add delimited escape sequences
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3353.htm
C++ proposal:
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0085r0.html
Allowing stricter alignment for atomic types
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3312.pdf
Case range expressions
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3370.htm
Named loops
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3355.htm
Other possibly interesting features:
Strong typedefs
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3320.htm
Tail recursion for preprocessor macros
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3307.htm
Jens
Received on 2024-11-06 12:24:07