On Sun, 10 Dec 2023 23:47:19 +0000, Alejandro Colomar <alx@xxxxxxxxxx> said: > Yeah, I'm thinking in 50 years from now, assuming all implementations > have good intentions and don't want to break programs just because the > standard says they can. Hopefully atoi(3) could be usable in half a > century; if the planet is still there. Sure, one can lead by example. I wouldn't hold my breath that everyone follows, though. I definitely predict maintainers (cough, some BSDs, cough) saying "nobody should use ato*() anyway". > BTW, regarding your blog post about strtoul(3), I don't think it's so > hard to parse unsigned integers. I couldn't reply to your blong without > logging in, but replied to the linked SO post: > <https://softwareengineering.stackexchange.com/a/449060/332848> Ah, parse it twice to check. Yeah I'd not thought of that. Thanks. I'll add an update. -- typedef struct me_s { char name[] = { "Thomas Habets" }; char email[] = { "thomas@xxxxxxxxx" }; char kernel[] = { "Linux" }; char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt"; }; char pgp[] = { "9907 8698 8A24 F52F 1C2E 87F6 39A4 9EEA 460A 0169" }; char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" }; } me_t;
