Falsehoods programmers believe about languages
Falsehoods programmers believe about languages
This is what we have to put up with in the software localisation industry.
I can’t believe nobody has done this list yet. I mean, there is one about names, one about time and many others on other topics, but not one about languages yet (except one honorable mention that comes close). So, here’s my attempt to list all the misconceptions and prejudices I’ve come across in the course of my long and illustrious career in software localisation and language technology. Enjoy – and send me your own ones!
You're viewing a single thread.
Every language has words for yes and no.
Assuming yes and no means true and false, c has numbers (1, 0) for yes and no and c++ can use those numbers for yes and no because it is a superset of c.
Technically, it's 0 and non-0 but I always use 1. They are integers rather than keywords.
The article is not about programming languages 🫠
Technically, 0 is false and anything else is true. !0 is 1, though, IIRC
As far as C goes, 1 is true and 0 is false.
In terms of POSIX exit codes, 0 is success and 1 is error.
I think more specifically for C, 0 is false and anything nonzero is true. Idk about NaN/inf.
True is anything other than zero in C.
Confidently incorrect.
Until you use exit codes, which flips the logic.
Jesus. I mistyped that horrendously to make a point about !0
I read my comment just now waking up and went wtf
That's what I meant so I've edited my comment to hopefully make that a bit clearer.Having actually tested it, because in C++ I use true/false, it is 0 that equals false and anything else is true. You'll have to forgive my lack of clarity. It's 03:02 and I've had about 2 hours sleep tonight and won't be getting any more. Time for a coffee.