On Wed, 24 Mar 2004, Stanislav Malyshev wrote: > Hm. Do you have some example of such code? Except for object cloning > issues which are application-wide and constructors won't help you there - > is there some class code that should be constructed differently in PHP5 > but behave exactly the same in all other aspects?
Doesn't have to be class code. Anything that has a behavioural change would qualify. Like array_merge() for example. If the legacy contructor code is calling array_merge() you might want to check that the args passed to the constructor are actually arrays before sending them on to the legacy code. But we are getting way off the real point which is the question of whether you should be allowed to call what I suppose is now the deprecated constructor directly or not. I don't see a good reason why it wouldn't be treated like a normal method in every way. In a few years when people who have never seen PHP4 happen to create a method with the same name as the class would get very confused if it didn't work I would think. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
