Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17890
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Status: good
DomainKey-Signature: q=dns; a=rsa-sha1; c=nofws;
	s=test; d=omniti.com;
	h=Received:In-Reply-To:References:Mime-Version:Content-Type:Message-Id:Cc:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer;
	b=Oz1a0ciKpYQi1WceTX5Fir63Gtjl3d4gbVtx3pXBBnJyzpU0rycsC2f2yIHdmhho
	Phj1x3ieIObVm6p6wrv9VQqxsm+0TvJItC3fzfG02xqQneYTqLWzDWLG4WeMmsbJ
In-Reply-To: <42FCE0E4.604@lerdorf.com>
References: <42FCE0E4.604@lerdorf.com>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <416F97E8-FE59-4297-B983-64E643939E3B@omniti.com>
Cc: George Schlossnagle <george@omniti.com>,
	internals <internals@lists.php.net>
Content-Transfer-Encoding: 7bit
Date: Fri, 12 Aug 2005 14:05:51 -0400
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Subject: Re: [PHP-DEV] PHP 6.0 Wishlist
From: george@omniti.com (George Schlossnagle)


On Aug 12, 2005, at 1:48 PM, Rasmus Lerdorf wrote:

> Since we are breaking a lot of stuff in 6.0, at least with
> Unicode_semantics=On I am wondering if it may not be time to break  
> some
> more stuff and do a bit of spring cleaning.  It would mean many apps
> would need some work to work on PHP 6, but at the same time I think it
> is work people would welcome since it would mostly involve removing
> hacks instead of adding them.  And yes, I know this is pretty
> controversial, so take a few deep breaths before replying, please.
>
> 1. Remove register_globals completely

+1

> 2. Remove magic_quotes_*

+1

> 3. Add input filter extension which will include a mechanism for
>    application developers to very easily turn it off which would swap
>    the raw GPC arrays back in case the site had it turned on by  
> default.

That seems a bit scary, and almost  as if it would defeat the  
purpose.  I'm all for an input filter extension, but it should be one  
that can't be easily neutered by (potentially malicious) applications.

> 4. Include an opcode cache by default.  A lot of work has gone into
>    pecl/apc recently, but I am not hung up on which one goes in.

+1


> 6. Remove some stuff that has been marked deprecated since PHP 3/4

+1.  I agree with Ilia that this should be done on a case-by-case basis.

> A couple of others that we could consider, but I don't actually think
> wins us much apart from academic purity (which I have never been all
> that keen on) are:
>
> 7. Make identifiers case-sensitive

+1

9. Radically change all the operator syntaxes.   Oh wait, that's Perl  
6.0, sorry.

George