* Nikos Chantziaras <rea...@arcor.de> schrieb: > Did it actually occur to anyone that warnings are not errors? You can > have them for correct code. A warning means you might want to look at > the code to check whether there's some real error there. It doesn't > mean the code is broken.
In my personal experience, most times a warning comes it, the code *is* broken (but *might* work in most situations). So, developers should always enable it and think ten times if some warning is acceptable. But: you all conviced me. These flags should be controlled by the distro buildsystem, not the individual package. Developers just should take care that there're no preventable warnings. cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ ---------------------------------------------------------------------
