690
This is my life now, until I finally understand Cmake.
(discuss.tchncs.de)
Which will probably be never.
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Aug 2024
690 points (98.5% liked)
Programmer Humor
19623 readers
1 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
That is such a bad idea. Better to have the compiler warn you about it like in Rust, or have the linter / IDE highlight it.
If it's going to compile without any warnings I'd rather the app crash rather than continue execution with rogue values as it does now.
There is so much room for things like corrupted files or undocumented behavior until it crashes. Without the compiler babysitting you it's a lot easier to find broken variables when they don't point to garbage.
Just enable all compiler warnings (and disable the ones you don't care about), a good C compiler can tell you about using unassigned variables.
Still learning, they just covered compiler flags in cs. They didn't go into detail yet though.
Edit: I've used python for years and they have something equally dumb. You can have a function in a massive application that is broken and the moment it's called, the application crashes.
At any other point the application will just run as if nothing is wrong even though python evaluates everything at runtime. I'm sure they can't do much because the initial launch would be slow.