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

[John W. Eaton]

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

Oh, now I see that the naming convention I proposed doesn't help with the case
of, for example, a constructor argument called "exit_status" and a member
function with the same name.  But that's not really a problem, which is why
the GCC maintainers dropped that warning.  OTOH, a function argument or a
local variable name that shadows a member variable *is* still flagged.

As for leading "_" vs "m_", I would prefer "m_" in Octave sources please (not
"_m").


    _______________________________________________________

Reply to this item at:

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

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