i stick to that rule too, and i like it as well. it's not that hard, and when followed, makes for easier coding, you can be sure that you're affecting the class var you want, instead of a random local var. i totally vote to stick with the rule, and *actually following it* :).
lisa On Sun, Nov 9, 2008 at 1:03 PM, nathan binkert <[EMAIL PROTECTED]> wrote: > >> - It's still the official policy that local variables are lower > >> w/underscores while class members are mixed case... sometimes I have > >> mixed feelings about that one myself but I've been trying to do a > >> better job of sticking with it. > >> > > I was actually under the impression that the underscore variables went > > in python and the camel case went in C++. My impression was that it was > > very inconsistent but that camel case was usually used. My vote would be > > to just get rid of that rule rather than pretend to keep following it. > > Why do we have the two different styles anyway? > > I follow this rule and I'd like to see it not go away. It's too easy > to write code and not know that you're affecting a class variable. > It's also easy to accidentally shadow a class variable and confuse > yourself if you accidentally name the same thing twice. So, I > personally think this is very good practice. > > The one place that we seem to have gravitated to lower case with > underscores is for statistics and python parameters. This is probably > a hold over from older versions of these things that we've just kept > sticking to. > > Nate > _______________________________________________ > m5-dev mailing list > m5-dev@m5sim.org > http://m5sim.org/mailman/listinfo/m5-dev > >
_______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
