@a1ba Child Porn Archive Network

@a1ba Although could also be Comprehensive Porn Archive Network, but that's basically bittorrent.

@lanodan Child Perl Archive Network

(letting children learn perl? that's even worse)

@a1ba Better than JavaScript
JavaScript for Kids.png

@lanodan or C

@a1ba @lanodan

@a1ba@suya.place @lanodan@queer.hacktivis.me It's a good book.

@SuperDicq @a1ba The one I use is typically this one (latest C23 draft).
screen.png

@allison @lanodan @a1ba much less traumatizing than knowing that a segfault is the nicest and safest possibility when writing past allocated memory in C

@affine @allison @lanodan exactly why one of my colleagues once said that crash is a best outcome of a bug

@a1ba @allison @affine Yeah, it's why I tend to add a bit of asserts for "nope, no way this can happen, so if it did, better crash"

@lanodan @allison @affine just don't do asserts that can be disabled with NDEBUG/enabled with _DEBUG nonsense

@a1ba@suya.place @allison@hidamari.apartments @affine@mitra.hollow.capital Yeah, I have -DDEBUG -UNDEBUG in my cflags to avoid that nonsense.

Also no asserts when it could be regular error handling instead.

@lanodan @SuperDicq @a1ba n3220 is now recommended for C23, first one post the release AFAICT

@mirabilos @lanodan @SuperDicq world if ISO just let download final standard versions

@lanodan @allison @affine @a1ba Please don't run asserts in production

@ska @lanodan @allison @affine I would rather have them in production as sort of lazy error handling than blow up production because of a missing check that "should never trigger"

@a1ba@suya.place @allison@hidamari.apartments @affine@mitra.hollow.capital @ska@social.treehouse.systems I find having the proper error handling to be better, specially that way there's less chances of having screwed the function return types / parameters which can then means refactoring headaches or worse in case of a library where you want to avoid ABI breaks.

Plus you can often just if(oh_no) return -1; and call it a day.

@a1ba @affine @allison @ska Meanwhile one case where I use assert is to make sure there won't be nonsense from the compiler, like parts of code which should be unreachable.
Or things like poor man's bound checking.

And I often feel like assert should be banned from libraries, specially ones that aren't internal to a project.