Also,
> CRuby actually ships with 90 encodings (as of 3.3)
This is asinine.
>This is asinine.
Overall there are even more: 103. But then again 1.9.2 only has 85 and 95 overall. Also one of those new 'overall' ones is the EBCDIC code page for US/Canada.
nullptr is an overkill solution. The ambiguity could have been solved by mandating that NULL be defined as (void*)0 rather than giving implementations the choice of (void*)0 or 0.
>Although it would have been a bit of a pain to adapt,
>an '89 or '99 standard in which the only source representation
>of the null pointer was NULL or nil or some other built-in token
>would have had my approval.
https://groups.google.com/g/comp.std.c/c/fh4xKnWOQuo/m/IAaOe...
Sargon is anti identity politics and a classic, free speech pro-capitalist liberal. I'm not sure where you take your information from
He's not even a good source of information as his 3 hours long videos consist of Wikipedia articles he glanced through and repeating extreme right-wing conspiracies (Cultural Marxism, the terrorist attack at the Unite the Right rally).
(Also the only decent anti-idpol people are Marxists.)
>FILE Encapsulation: In previous versions, the FILE type was completely defined in <stdio.h>, so it was possible for user code to reach into a FILE and muck with its internals. We have refactored the stdio library to improve encapsulation of the library implementation details. As part of this, FILE as defined in <stdio.h> is now an opaque type and its members are inaccessible from outside of the CRT itself.
https://devblogs.microsoft.com/cppblog/c-runtime-crt-feature...