[Octave-bug-tracker] [bug #48493] Clear up "shadowed member" warnings

[John W. Eaton]

Follow-up Comment #10, bug #48493 (project octave):

I agree that function pointer names that conflict with member function names
would be a problem so I'm glad that GCC will still warn about those.

But for ordinary parameter names, it is a hassle, because one often wants a
member variable named FOO that with an accessor function (FOO seems like an
obvious name for that) and that may be passed as a construtor argument (FOO is
also an obvious choice for that name).  I'm willing to use m_FOO for the
member variable name.  I have used FOO_arg or xFOO in the past for parameter
names, but only because GCC was warning about it.  I'm happy to not have to do
that.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48493>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/