🚀 go-pugleaf

iwelch@agsm.ucla.edu (Ivo Welch) writes:

>Is it possible to selectively suppress just one warning in gcc? I have
>a class for  which I want to  define an interface  with functions that
>are identical to the variable names, e.g.,
>
>	class someclass {
>	 protected: int thisvar;
>	 public: thisvar() { return thisvar; }
>	}
>
>and I get tons of
>	warning: shadowing member `ex' with member function
>
>I am aware that   I could change  the name  of the members,  but would
>rather not.

Well, I would very strongly suggest that you do, because what you
are witnessing is actually a g++ bug - it should be an error, not a warning.
It is not legal to declare both a variable and a function with the same
name in the same scope. Other C++ compilers will correctly diagnose
this error.

-- 
Fergus Henderson                     This .signature virus might be
fjh@munta.cs.mu.OZ.AU                getting old, but you still can't
                                     consistently believe it unless you
Linux: Choice of a GNU Generation    copy it to your own .signature file!