C23 Implications for C Libraries
htmlpreview.github.io
C23 Implications for C Libraries
1–10 of 135 posts
Re: C23 Implications for C Libraries
#2Re: C23 Implications for C Libraries
#3Edit: Ugh, it needs javascript to render simple HTML.
Re: C23 Implications for C Libraries
#4Re: C23 Implications for C Libraries
#5Finally! My joy knows no bounds.
Re: C23 Implications for C Libraries
#6> Extended integer types may be wider than intmax_t
Re: C23 Implications for C Libraries
#7> Trigraphs are removed from the language. Finally! My joy knows no bounds.
They seem pretty harmless, are they difficult to implement?
Re: C23 Implications for C Libraries
#8The page gives a network error. Edit: Ugh, it needs javascript to render simple HTML.
Re: C23 Implications for C Libraries
#9That was already portable between 16 bit, 32 bit, 64 bit etc. Why is it that just because the compiler supports 128 bit or 256 bit integers that compiling in such a mode doesn't correspondingly update "[u]intmax_t"?
The linked page says they 'cannot be "extended integer types" in the sense of C17', but that printf() and scanf() should still support these?
Re: C23 Implications for C Libraries
#10"Extended integer types may be wider than intmax_t". I'm sure there's a good reason for this, but it was introduced in C99, which says (in 7.8.1.5): "[intmax_t] designates a signed integer type capable of representing any value of any signed integer type". That was already portable between 16 bit, 32 bit, 64 bit etc. Why is it that just because the compiler supports 128 bit or 256 bit integers that compiling in such…