3 ms·
People ignore warnings. Want proof? Go grab damn near any open source project and compile it. It's almost guaranteed that the default compile options, chosen by
by jff 13y ago
People ignore warnings. Want proof? Go grab damn near any open source project and compile it. It's almost guaranteed that the default compile options, chosen by the authors, will generate dozens if not hundreds of warnings. Everyone's so very noble at the start of a project, "We shall turn on all warnings, and then fix them!", but really once the program compiles and seems to run properly, all that goes out the window.
- zzzcpan 13y agoPerl is one example, where people usually have all warnings enabled and keep their code warning-free. I guess it depends on the community.
- ridiculous_fish 13y agoThis is largely due to compiler version differences. I can fix every warning my compiler emits, and you are likely to still get warnings on yours. Go's enforced -Werror can work in a smallish community, where there's a single compiler and a culture of everyone always using its latest version. But I don't see how it can survive an environment where there's multiple compilers, each with multiple versions. Who here could write a C program that is guaranteed to never produce a warning on any C compiler?