Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41713
Return-Path: <bdavies@stickyeyes.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 78500 invoked from network); 6 Nov 2008 11:45:24 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 6 Nov 2008 11:45:24 -0000
Received: from [127.0.0.1] ([127.0.0.1:21717])
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ECSTREAM
	id E6/A8-35522-4D8D2194 for <internals@lists.php.net>; Thu, 06 Nov 2008 06:45:24 -0500
Authentication-Results: pb1.pair.com smtp.mail=bdavies@stickyeyes.com; spf=permerror; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=bdavies@stickyeyes.com; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain stickyeyes.com from 195.177.193.141 cause and error)
X-PHP-List-Original-Sender: bdavies@stickyeyes.com
X-Host-Fingerprint: 195.177.193.141 www.stickyeyes.com Linux 2.6
Received: from [195.177.193.141] ([195.177.193.141:56491] helo=globalgold.co.uk)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 02/A8-35522-848D2194 for <internals@lists.php.net>; Thu, 06 Nov 2008 06:43:06 -0500
Received: (qmail 4064 invoked from network); 6 Nov 2008 11:43:01 +0000
Received: from stickyeyes.plus.com (HELO BenPC) (84.92.224.196)
  by www.stickyeyes.com with SMTP; 6 Nov 2008 11:43:01 +0000
To: "'Steph Fox'" <steph@php.net>,
	"'Dan'" <iammrdan@googlemail.com>,
	"'troels knak-nielsen'" <troelskn@gmail.com>
Cc: "'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>
In-Reply-To: <007301c93ffe$f4b5ad80$3ffc1f3e@foxbox>
Date: Thu, 6 Nov 2008 11:43:03 -0000
Message-ID: <029101c94004$d4564440$7d02ccc0$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ack//rIocpnYPfE9TjepUOC9k6pgOwABUySg
Content-Language: en-gb
Subject: RE: [PHP-DEV] Call it: allow reserved words in a class or not?
From: bdavies@stickyeyes.com ("Ben Davies")

> 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=20
> it's
> a Helper for Arrays in the MyFramework framework. I shouldn't need to=20
> suffix
> the class name with 'Helper' to reconfirm that, just because the PHP=20
> engine
> doesn't like it.

"This thread really should be re-titled to "allow reserved words as a=20
classname or not". Then perhaps the only logical response to the =
question=20
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,=20
West One,=20
Wellington Street,=20
Leeds, LS1 1BA=20
Email: ben@stickyeyes.com=20
0113 391 2929 | <telephone> | Fax 0113 391 2939=20
=A0=20
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]=20
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=20
> it's
> a Helper for Arrays in the MyFramework framework. I shouldn't need to=20
> suffix
> the class name with 'Helper' to reconfirm that, just because the PHP=20
> engine
> doesn't like it.

This thread really should be re-titled to "allow reserved words as a=20
classname or not". Then perhaps the only logical response to the =
question=20
would be so obvious that there would be no thread... oo-er...

- Steph=20