Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41721
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.134.184 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=Zyj5ziwD2AuOzOIl37bjmZIDh/V3HO3ZqCgHdNlbRz+e7EV8kfUpM1DcjZOBEOm8Zw
         d7hwclhlmAxgAt5cxCw/ZS8aGyR3f1/0DbLx8kURLAIAG47Gw3PBEtY6S8HfCY3yRyiz
         J7bkn6lVoRdhYhpBAbpK4xrFhiZfT2Hbxu3Zk=
Message-ID: <8cf711460811060435p238fe874n7a690703661096d3@mail.gmail.com>
Date: Thu, 6 Nov 2008 12:35:45 +0000
Sender: mikko.koppanen@gmail.com
To: Dan <iammrdan@googlemail.com>
Cc: "Steph Fox" <steph@phparch.com>, internals@lists.php.net
In-Reply-To: <cd3112cc0811060415h1613269dx903f1db0f7b6dee2@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4EA88C3A8A2747989925A5D21448FCE7@pc>
	 <200811052154.29537.larry@garfieldtech.com>
	 <cd3112cc0811060135t66b579e7i396e5ad8c67cff6f@mail.gmail.com>
	 <98b8086f0811060150p2fb0312dj66896cb227c871ec@mail.gmail.com>
	 <cd3112cc0811060203r10927444xa19669fa37a0dc8a@mail.gmail.com>
	 <007301c93ffe$f4b5ad80$3ffc1f3e@foxbox>
	 <029101c94004$d4564440$7d02ccc0$@com>
	 <cd3112cc0811060353o2d3b37fbrb75d5da8007bb79d@mail.gmail.com>
	 <013b01c94007$b66d60a0$3ffc1f3e@foxbox>
	 <cd3112cc0811060415h1613269dx903f1db0f7b6dee2@mail.gmail.com>
Subject: Re: [PHP-DEV] Call it: allow reserved words in a class or not?
From: mikko@ibuildings.com ("Mikko Koppanen")

On Thu, Nov 6, 2008 at 12:15 PM, Dan <iammrdan@googlemail.com> 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