JM>>1. __get/__set are too cumbersome for simple use cases. (Hence this
JM>>thread)
This thread is in no way "simple use case".
JM>>2. __get/__set is slow. (In the best case: about 10x slower than simple
JM>>property, 3x slower than an accessor method call)
Slow as opposed to calling different function for different properties,
adding additional lookups on each access?
JM>>individual properties, just as you can in Java, C#, Ruby, Delphi,
JM>>Python, Visual Basic, Objective C, Smalltalk, and sometimes C++. (To
JM>>the best of my knowledge.) Read only is a special case of this
JM>>capability.
This would be, however, yet another level of complexity added to the
language...
--
Stanislav Malyshev, Zend Products Engineer
[email protected] http://www.zend.com/ +972-3-6139665 ext.115