On Thu, Nov 6, 2008 at 12:15 PM, Dan <[EMAIL PROTECTED]> wrote: > Okay, I'm not going to sit and argue it... but to anyone looking at these > issues from outside the PHP internals world (like I am), that argument is > worthy of ridicule.
What argument? Due to top-posting you're kind of killing the ability to follow the thread. > PHP may be a hybrid language, but the fact is you're implementing object > oriented functionality, and as such should be implementing it in a way that > follows de-facto standards in object oriented language design. I should be > able to overload your internal array object, and yes, arraysshould be > objects. Wouldn't this mean that also primitive types such as integer and string should be objects? Doing something like this would break about all the code out there without a major gain. One of the strenghts of PHP is that it balances well between procedural and object oriented approaches. There is ArrayObject, ArrayAccess etc for people who wish to use OO and array for the people who don't. > Javascript would be a prime example of a non-standard object oriented > approach, and yet that still manages to support the basics in a way that > make sense. > I think you are missing a point here. PHP is not Javascript or .NET. -- Mikko Koppanen -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
