Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39355
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 88.198.8.16 as permitted sender)
Message-ID: <2276F557-CBE3-4F69-B2C5-C7EE16647847@php.net>
To: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@php.net>,
 PHP Internals List <internals@lists.php.net>,
 Antony Dovgal <tony@daylessday.org>
In-Reply-To: <1217070146.3105.83.camel@goldfinger.johannes.nop>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Sat, 26 Jul 2008 22:17:52 +0200
References: <1217070146.3105.83.camel@goldfinger.johannes.nop>
Subject: Re: [PHP-DEV] towards 5.3 alpha1
From: lsmith@php.net (Lukas Kahwe Smith)


On 26.07.2008, at 13:02, Johannes Schl=FCter wrote:

> - undeprecate ticks: as long as we have no replacement for the signal
>  handling we shouldn't deprecate the only way to do that.

So currently the deprecation warning reads that the feature will be =20
removed in PHP 6. We could also tone down the message to not mention a =20=

specific PHP version for removal. Derick, Marcus, Jani etc have all =20
said that they have seen reports of serious issues aka crashes with =20
ticks. Tony says he is using tick's and we do not have a replacement =20
to offer. But given the fact that even Tony did not come out to say =20
that he knows how to fix ticks, it seems like the best compromise is =20
to deprecate ticks with a message that it could get removed in any =20
minor version release with or without a replacement, but it will kept =20=

for now.

> - drop __toString() from Closures
> - Do not include 3xx http codes in the fopen wrapper change


Can we get a quick in formal vote on each of the above items?

regards,
Lukas Kahwe Smith
smith@pooteeweet.org