Am 28.06.2014 11:30, schrieb Jacob Carlborg:
On 2014-06-28 08:19, dennis luehring wrote:
thx for the examples - never though of these problems
i personaly would just forbid any shadowing and single-self-assign
and then having unique names (i use m_ for members and p_ for parameters
etc.) or give a compile error asking for this.x or .x (maybe problematic
with inner structs/functions)
I think, in general, if you need to prefix/suffix any symbols name,
there's something wrong with the language.
i agree 100% - i just try to overcome the shadowing clean with this AND
have also scope information in the name (i just want to know at every
palce in code if someing is an parameter)
but i would always prefer a better working method
