Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50454
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender)
Date: Tue, 23 Nov 2010 14:53:26 +0000 (GMT)
To: Matthew Weier O'Phinney <weierophinney@php.net>
cc: PHP Developers Mailing List <internals@lists.php.net>
In-Reply-To: <C4.22.28185.25ACBEC4@pb1.pair.com>
Message-ID: <alpine.DEB.2.00.1011231448580.24401@kossu.derickrethans.nl>
References: <AANLkTi=coWEEMNnr_SsTCo7HaXUPRwcJg7fUz=NjA8nq@mail.gmail.com> <alpine.DEB.2.00.1011230945310.24401@kossu.derickrethans.nl> <C4.22.28185.25ACBEC4@pb1.pair.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] Hold off 5.4
From: derick@php.net (Derick Rethans)

On Tue, 23 Nov 2010, Matthew Weier O'Phinney wrote:

> On 2010-11-23, Derick Rethans <derick@php.net> wrote:
> > On Mon, 22 Nov 2010, Felipe Pena wrote:
> > > . classes named as any of the type hint scalar types
> > > do not work anymore
> > > aka class int {}
> >
> > Yeah, there is a slight hint of a BC break in case you have a class 
> > named "int" or "float" etc. But there is:
> > http://uk.php.net/manual/en/userlandnaming.tips.php
> >
> > Perhaps we can reduce the current list of classes:
> > int, integer, real, double, string, binary, scalar, array, object, 
> > bool, boolean
> > to what the manual uses though (for prototypes):
> > int, float, string, binary, scalar, array, object, bool
> > (Point #18 at http://doc.php.net/php/dochowto/chapter-conventions.php)
> 
> Sorry, but this is actually a pretty grave BC break.
> 
> Currently, you can do the following:
> 
>     namespace Foo\Validator;
> 
>     class Int {}

During our namespace discussion, this is exactly what I warned about. In 
order to make use of namespaces, you need to have atleast two "elements" 
in your class names otherwise we can still never introduce a new class. 
But that was not listened too.

> As Sebastian noted, it seems this should be addressed with the new
> lexer; I'd argue that if the current type hinting must introduce new
> keywords, it should wait until the new lexer is in place in order to
> insulate end-users from such changes.

The new lexer however, is a slower; so not a viable solution right now.

> With a defined release process, *everyone* knows what must be done, by 
> when, making the process more transparent and *gasp* democratic.

Well, I don't think we've ever been democratic. I probably think 
that that wouldn't even work. Also, I think an alpha has pretty much 
been announce nicely on time for people to know what's happening. 

Derick

-- 
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug