Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41716
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain phparch.com from 64.99.136.181 cause and error)
Message-ID: <013b01c94007$b66d60a0$3ffc1f3e@foxbox>
Reply-To: "Steph Fox" <steph@phparch.com>
To: "Dan" <iammrdan@googlemail.com>,
	"Ben Davies" <bdavies@stickyeyes.com>
Cc: "troels knak-nielsen" <troelskn@gmail.com>,
	"Larry Garfield" <larry@garfieldtech.com>,
	<internals@lists.php.net>
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>
Date: Thu, 6 Nov 2008 12:03:39 -0000
Organization: php|architect
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Call it: allow reserved words in a class or not?
From: steph@phparch.com ("Steph Fox")

> In .NET, I can stick an Array class into my own namespace, extending the
> System.Array type if I want to and use it in my code without issue. Why 
> can
> I not do that here? Is it simply that you're so worried about backwards
> compatibility that you feel that you can't make the necessary changes to 
> the
> language to implement something fully?

.NET is an object oriented language. It has something called System.Array.

PHP is a hybrid language. It does not and hopefully never will have 
something called System.Array.

It's like the difference between English and Esperanto... and you're telling 
us 'cough' should rhyme with 'cow' because that's how Esperanto would have 
it. But English is so much easier to learn, if more difficult to master, 
that it's become the lingua franca for the 'net.

- Steph


>
> Dan
>
>
> On Thu, Nov 6, 2008 at 11:43 AM, Ben Davies <bdavies@stickyeyes.com> 
> wrote:
>
>> > Isn't the ability to do that one of the biggest reasons for having
>> > namespaces? To avoid having to fill your class names with junk.
>> > The examples are namespaced appropriately, they tell the developer that
>> > it's
>> > a Helper for Arrays in the MyFramework framework. I shouldn't need to
>> > suffix
>> > the class name with 'Helper' to reconfirm that, just because the PHP
>> > engine
>> > doesn't like it.
>>
>> "This thread really should be re-titled to "allow reserved words as a
>> classname or not". Then perhaps the only logical response to the question
>> would be so obvious that there would be no thread... oo-er..."
>>
>> I think you might be deliberately missing Dan's point here: array is a
>> reserved word because it is not namespaced. If the PHP native function
>> array() was namespaced to PHPCore\array() then Dan could create a class 
>> or
>> function called array under his own namespace. This is exactly what
>> namespacing affords us.
>>
>> array() is only a reserved word because it is not a directly accessable
>> native datatype. If array() was an object Array, this wouldn't be a
>> problem.
>>
>> This namespaces issues highlights the very fundamental issues with PHP, 
>> and
>> glib, childish responses like yours only serve to score points.
>>
>> Grow up and join the conversation.
>>
>>
>> Ben Davies | Lead Developer | Stickyeyes
>> 6th Floor,
>> West One,
>> Wellington Street,
>> Leeds, LS1 1BA
>> Email: ben@stickyeyes.com
>> 0113 391 2929 | <telephone> | Fax 0113 391 2939
>>
>> This e-mail may contain information that is privileged, confidential or
>> otherwise protected from disclosure. It must not be used by, or its
>> contents
>> copied or disclosed to persons other than the intended recipient. Any
>> liability (in negligence or otherwise) arising from any third party 
>> acting,
>> or refraining from acting, on any information contained in this e-mail is
>> excluded. The views expressed may not be official company policy, but
>> instead, the personal views of the originator. If you have received this
>> e-mail in error please notify the sender and delete the e-mail.
>>
>>
>>
>> -----Original Message-----
>> From: Steph Fox [mailto:steph@php.net]
>> Sent: 06 November 2008 11:01
>> To: Dan; troels knak-nielsen
>> Cc: Larry Garfield; internals@lists.php.net; ben@stickyeyes.com
>> Subject: Re: [PHP-DEV] Call it: allow reserved words in a class or not?
>>
>> > Isn't the ability to do that one of the biggest reasons for having
>> > namespaces? To avoid having to fill your class names with junk.
>> > The examples are namespaced appropriately, they tell the developer that
>> > it's
>> > a Helper for Arrays in the MyFramework framework. I shouldn't need to
>> > suffix
>> > the class name with 'Helper' to reconfirm that, just because the PHP
>> > engine
>> > doesn't like it.
>>
>> This thread really should be re-titled to "allow reserved words as a
>> classname or not". Then perhaps the only logical response to the question
>> would be so obvious that there would be no thread... oo-er...
>>
>> - Steph
>>
>>
>