C,
It was never designed by committee from the start; it was retroactively documented after it had already been used for 20 years.
which explains, a-lot.
@avrldotdev literally was just an early UNIX library function that got used in C more than once, so it ended up becoming part of C. (because unix was basically the entirety of all C code at that point)
@avrldotdev NO NO NONO NO NONO NO NONO NO NO
NOT GETS
NO NO NONO
tbf gets was written in like 1969 for pdp7 in asm, and was NOT intended of being used long term.
(deprecated in C99, removed in C11)
"it might break old software"
old software, that uses UB as a feature........
its not C code if it breaks the standard.
granted emulators need wrapping, which is what attributes and setting the exception vector is for.
I don't get the hype around Rust/Go/Zig/FilC replacing C.
Yeah, C has problems, but most things todo with safety (the main point) are undefined behavior.
So, why not just implement safer emitted behavior instead of rewriting everything?
Its legitimately the compiler's fault.
@_dtx___@gabefollower I mean i guess its cool;
there isn't that much point though unless say a declaration is over 1000 lines away and your only tool is `vi`, and need to figure out it's type.
@valigo is AT&T like that literally so in ye old days they could get source before dest so they could emit properly?
(unix V2 source for reference, old unix (1970s) world code was crazy)
https://t.co/uaZk6da0cR
(from the compiler, or early opt? i think?)
old compilers were crazy
So, AI means we have to pay an annoying amount of conscious effort to see truth on the platforms that allow it.
on twitter you don't even need to check though,
is it an image?
>its ai, about 80% of the time
the problem with ai images:
is that yeah its really obvious.
but most of the time its 400 pixels on a zoomed out frame where you cant see finer detail (or lack there of).
e.g. a controller's buttons being all funky but they encompass >5% of the image.