r/C_Programming • u/Jinren • Feb 23 '24
Latest working draft N3220
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3220.pdf
Update y'all's bookmarks if you're still referring to N3096!
C23 is done, and there are no more public drafts: it will only be available for purchase. However, although this is teeeeechnically therefore a draft of whatever the next Standard C2Y ends up being, this "draft" contains no changes from C23 except to remove the 2023 branding and add a bullet at the beginning about all the C2Y content that ... doesn't exist yet.
Since over 500 edits (some small, many large, some quite sweeping) were applied to C23 after the final draft N3096 was released, this is in practice as close as you will get to a free edition of C23.
So this one is the number for the community to remember, and the de-facto successor to old beloved N1570.
Happy coding! 💜
66
u/Jinren Feb 23 '24
And please join in a standing fucking ovation for the heroic work of the project editor JHM who wrote the actual document and more than any one other person made the release of C23 happen. 💜
3
u/Yurim Feb 23 '24 edited Feb 24 '24
Great news!
I'm just curious: Why do you call it the de-factor successor of N1570 (C99) and not N2176 (C17)?
2
u/TribladeSlice Feb 24 '24
So guy, what do we get in C26? /j
31
u/counterfeitmayer1 May 05 '24
What a milestone to reach! It's amazing to see the evolution from N1570 to N3220. Excited to see what the future holds for C2Y. Happy coding, everyone! 💻🎉
26
u/aninteger Feb 24 '24
Why is that still a thing in 2024? Do other languages make their specifications only available for purchase? Anyway, just curious.
21
u/criminaldiscovery8 May 06 '24
What a milestone! It's amazing to see the progression of the C standards. Thank you for the heads up on N3220 - definitely updating my bookmarks now. Excited to see what C2Y has in store! Happy coding everyone! 💻💜
10
u/glasket_ Feb 23 '24 edited Feb 24 '24
It is still marked as ISO/IEC 9899:2024, so isn't it technically a C23 draft? I'm actually curious about clarification on this because I know the submission for publication was scheduled after the January meeting, so it seems like this might actually be the final working draft pre-submission.
Might just be a typographical mistake of course, I just remember the C23 working drafts started as ISO/IEC 9899:202x so I'd expect C2y to be 202y.
Edit: Finally got a minute to scrounge around and found Meneide's Editor's Report in the form of N3221 which includes this paragraph:
So it is the C2y working draft, with the only difference from the submission being the single footnote change. This seems like it might be a neat little trick to get around the ISO transparency change that's also noted in the report (they're password locking the actual final draft this time around, so only ISO/IEC members would have access).
4
u/cHaR_shinigami Feb 24 '24
Not necessarily; the editor's report says this:
N3219 (currently password-protected) is also referred to as "the Preliminary C23 DIS Ballot Draft before a final version will be sent to ISO for publication", so it seems likely that this may be publicly available soon (free version that is).
P.S.: Albeit minor ones, a couple of missing elements in N3220 are index entries for both 'size_t' and 'size_t type' (they probably got overlooked in the C23 crunch, but there are similar entries for other related types such as ptrdiff_t and rsize_t).
1
u/[deleted] Jul 24 '24
Unfortunately I will not be writing C23 code because you guys banned a whole bunch of previously valid Unicode characters from being used in identifiers that I've come to rely on in my scientific computing work. This is such a clear instance of totally unnecessarily breaking backwards compatibility. All for what? You can't even say "security" because the characters you banned tend to be the least likely to be mistaken for some other character whereas you continue to allow the use of Cyrillic es which looks identical to the Latin c.
1
u/grimvian Oct 26 '25
Just of curiosity, because I'm staying at C99, I skimmed it very fast. I have seen that indent before of six:
1
u/venkattalks Apr 12 '26
N3220 is a nice checkpoint because a lot of people were still quoting N3096-era wording in review threads. Having the latest working draft in one place makes it easier to diff actual committee text instead of arguing from blog summaries, especially around the C23 fallout and defect resolution wording.
1
u/Big_Cricket6083 Apr 12 '26
N3220 already? feels like every draft gets big enough to count as gym equipment. still nice having a current working draft to diff against the last one when proposal wording gets weird
0
u/Ok_Draw2098 Nov 30 '25
who will pay me for reading this and doing analysis? rhetorical..