> Out of curiosity, what is the reasoning behind removing the > comparison? It seems that being more explicit isn't a bad thing.
Well, it's explicit vs verbose. I think Steve and I see it as unnecessary verbosity because the language already implies the comparison. You could argue that the null comparison is useful, but certainly the true/false comparison just says something with more characters than another syntax alternative does. You could say this-> everywhere you access an instance variable, but it's just unnecessarily verbose. (Ruby actually chose to do m_ instead of this-> because it was shorter I guess). Yes, there are sometimes you have to use this-> in C++ and some dynamic languages require this sort of thing but when it is unambiguous, why bother? Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
