#standardc — Public Fediverse posts

I might have to release #djbwares 12 hot on the heels of 11.

Bloody C.

#StandardC

@ermo

Excellent news! Thank you.

The warnings are mainly Bernstein's buffer library relying upon being able to use one function pointer to point to multiple different functions with different signatures (which is a shenanighan that one could play with old C, but soon no longer) and Bernstein's byte library using char pointers.

I've fixed a load of places where the Bernstein code was blasé about function signatures. Those are two of the remaining unfixed areas.

#djbwares #StandardC

A bonus top tip for today:

'\376' will not compare equal to a character in memory with the value 254.

This is not assembly language, where one can compare an 8-bit byte with an 8-bit constant and have it just work, willy-nilly.

That would be crazy.

#djbwares #dnscache #octal #StandardC

@blinry @b0rk

You really should tell the #BusyBox people about that C bug in the feature autodetection.

I recently had to update a whole lot of K&R code (written a decade after C89) for similar reasons. I even had a similar autodetection break.

C99 has and C23 is even more going to hit a lot of old codebases where people wrote things K&R style, sadly in the cases of many of them well after #StandardC came into existence.