cremno
Joined 14 years ago
Karma
2,645
Submissions
307
Member since
Mar 24
Recent submissions
Comment · 1 year ago
Comment · 2 years ago
Besides fixing bad C code: how many of those packages are still properly maintained? The Ruby ones don't seem to be. Fedora and other distros likely have to build their packages with patches.
Comment · 3 years ago
>> CRuby actually ships with 90 encodings (as of 3.3)
>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.
Comment · 3 years ago
dmr would've approved of going a step further - only nullptr, no 0 and (void*)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...
Comment · 3 years ago
It's weird because even the first C standard was influenced by C++: function prototypes and const.
Comment · 8 years ago
People just have to look at the politicians and parties he's supporting. For example in the last French presidential election he opposed the pro-capitalist liberal (redundant as liberals are by definition pro-capitalism). I wonder what's his opinion on the Brazil one. A moderate social democrat vs. fascist belonging to a party called the "Social Liberal Party"?
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.)
Comment · 8 years ago
>liberal-communism
What's next? Anarcho-Capitalism?
Comment · 8 years ago
Comment · 8 years ago
It's also kinda ironic because improved performance was the reason behind that decision.
>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...