For the record, the advantages and disadvantages of variable name constructors were clear from day one, this issue has been hashed way before PHP even had OO. Your opinion was that it'd be better to have a common name, and eventually the discussion about the revised OO model suggested that it's probably a good idea, but there was really nothing new about the pros/cons that were raised, and variable name constructors still don't really pose any serious problem or barrier to writing just about any piece of code. It's no coincidence that the two most commonly used OO languages have variable name constructors, and people live fine with it :)
At 12:14 09/04/2002, Kristian Koehntopp wrote: >On Mon, Apr 08, 2002 at 11:49:23AM -0500, Andrei Zmievski wrote: > > __get_x() is simply a shortcut, I don't see how it can > > backfire on us in the overload framework. > >Nor can I, at the moment. > >But then, nobody did see how variable constructor names could >possibly backfire on us with a concrete example, nor were >registered globals generally considered a bad idea when they >were introduced. -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
