> > (Note that this is another flaw in Brad's argument for allowing > the empty parentheses to be left off of method function calls. > This is another visible difference between the behavior of a > member defined as a class method versus a class property. > The "Uniform Access Principle" is already invalidated.) > For what it's worth, I would support removing the "optional" empty parens on calls of class methods with no arguments. We should require those parens under all circumstances, for clarity and readability at call sites. It's also more uniform and lends itself positively to name resolution, as Steven alluded to in his post. I am not a fan of the "Uniform Access Principle". Regards, DougReceived on Mon Jun 5 20:29:28 2006
This archive was generated by hypermail 2.1.8 : Mon Jun 05 2006 - 20:29:45 PDT