On 21/03/13 11:00, Mike McCormack wrote: > On 03/21/2013 09:25 PM, Tom Hacohen wrote: > >> Silencing warnings just for silencing is not good. We use them to spot >> bugs, that's why we like them so much. Silencing useful warnings is >> counter-productive. > > Usually a developer, upon checking out a code base and building it on > their system and observing a nice warning free compile will have a sense > of confidence in a project. > > Usually a developer, on making a modification to their code, checks for > warnings and makes sure none have been introduced before pushing their code. > > There are some people who wish to compile their code with every frickin > warning in the world turned on, then proceed to ignore said warnings, > and commit code with warnings to their revision control systems. >
Mike, You are forgetting the most typical case in efl land .... developers who do not even Compile their code before commit ;) (Sorry, just had to chime in with that ;) Please, ignore that I was even here) dh > That gcc somehow changed which warnings it emits in a newer version > changes none of the above. > > Enjoy your warnings. > > Mike > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
