C Strings: A 50-Year Mistake – By Trần Thành Long
rbanffy
12 points
3 comments
July 15, 2026
Related Discussions
Found 5 related stories in 656.2ms across 14,015 title embeddings via pgvector HNSW
- C programmers commit fresh crimes against readability jjgreen · 13 pts · July 05, 2026 · 51% similar
- C programmers commit fresh crimes against readability Bender · 126 pts · July 06, 2026 · 51% similar
- Unsigned sizes: A five year mistake lerno · 77 pts · May 02, 2026 · 51% similar
- The Little Book of C ghostrss · 65 pts · March 26, 2026 · 46% similar
- C++: The Programming Language back cover raises questions not answered by front paulmooreparks · 54 pts · June 06, 2026 · 44% similar
Discussion Highlights (2 comments)
kestermckinney
when i first started programming in the early 90s we had someone on our team keep adding strcat("this string", NULL); His name was Karl. Every time we saw bad coding practices we called it Karl code.
matheusmoreira
In my projects I tried pretty hard to remake the world and get rid of C strings. Went all in on freestanding C, got rid of the standard library, developed my own abstractions. But I just didn't quite make it. The operating system interfaces want C strings. Can't even open a file without C strings. To fully exorcise C strings, I would need to reinvent Linux. I haven't got enough lifetimes for the task. Ended up tacking on a hidden trailing NUL to every single buffer instead.