> except a lot of programs never check for NULL. they just compare whatever crypt() gives back with the stored field, hit the NULL, and crash
> so musl (the libc under alpine) goes ok fine, crypt() just won't return NULL anymore. if it fails, it returns a single character instead.
Considering it's been accepted that crashing if malloc returns a NULL is your fault, did musl really feel the need to accommodate bad implementations like this or is this just AI dribble?
[1] https://hachyderm.io/@damienmiller/117563026759098135
As in: "Actually out there"
The hypothetical Alpine exists, yes, but what runs that like that?
> so musl (the libc under alpine) goes ok fine, crypt() just won't return NULL anymore. if it fails, it returns a single character instead.
Considering it's been accepted that crashing if malloc returns a NULL is your fault, did musl really feel the need to accommodate bad implementations like this or is this just AI dribble?
You can use \ to escape formatting.
[0] https://news.ycombinator.com/item?id=50377221
"tl;dr" was a bit of a downgrade though, but that's fine