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 50.5ms across 5,215 title embeddings via pgvector HNSW
- Marketing failure: I thought I was building a C replacement. I was wrong lerno · 15 pts · August 16, 2026 · 53% similar
- Netstrings (1997) signa11 · 31 pts · July 16, 2026 · 42% similar
- An ambiguity in c89 which will never be fixed runningmike · 15 pts · August 10, 2026 · 41% similar
- C++26: Standard Library Hardening Experiments ibobev · 81 pts · August 31, 2026 · 40% similar
- CobaltC – The Successor to C? SilentLambda · 13 pts · August 31, 2026 · 40% 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.