On Mon, Jan 14, 2013 at 11:01 AM, Mike McCormack <mi...@ring3k.org> wrote: > On 01/14/2013 11:15 PM, Lucas De Marchi wrote: > >> On Fri, Jan 11, 2013 at 7:40 PM, Enlightenment SVN >> <no-re...@enlightenment.org> wrote: >>> Log: >>> efl: Avoid shadow warnings (signal -> sig) >>> >>> Signed-off-by: Mike McCormack <mi...@atratus.org> >> >> >> Though I don't care too much about changes this (and thus it's ok to >> let it like it is now), this is instead a GCC bug. I'm not sure what >> is the version in which it was fixed... maybe 4.5 or 4.6. Are you >> using GCC 4.4? > > Hi Lucas, > > I'm using Ubuntu 12.04.1 LTS with gcc version 4.6.3 (Ubuntu/Linaro > 4.6.3-1ubuntu5). > > Whether it's a gcc bug or not, the point of having a warning free > compile is to: > > A) show other developers that having a warning free build is valued > > B) help your developers find real problems exposed by warnings by > keeping the warning noise as minimal as possible. > > Using -Wshadow, -Wunused-parameter, -Wunused-result and other noise > generating warnings is a waste of time unless you're prepared to fix all > the warnings that are shown up, especially on commonly used systems like > Ubuntu.
except if the compiler is buggy, too. Otherwise I agree with you (another reason why I always use -Wno-unused-parameter whenever I can). Lucas De Marchi ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
