Hi!
If you treat ::$ as a single construct in your mind then you will get classname::$foo() wrong. Of course the rule is that classname::.....() is a method call but it's less evident by just looking at the code.
It's really not that hard. It'd take you 1/100 of the time you are wasting discussing it to learn it, and that's counting only your time.
I have suggested that removing the $foo() construct completely, $foo(), $bar->$foo(), bar::$foo() all would solve this and although it breaks backwards compatibility, there is a perfect replacement by using call_user_func() instead.
That will not happen. There's tons of downsides and not one single upside to it.
I have implied that PHP does not care about backwards compatibility breaking and this especially will be true for the next release. This was supported by my experience working with various PHP versions over many years.
This is plain false. PHP does care for BC a lot. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
