Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50485
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=Iei0/Lul93q4Iqu+VsaGkY4kLjINAMQ6M/3lI4T+J0E3+KoB1TfOZsTDBVzH3d5InR
         LZTNbN3akHKwNIUkOcrupOq7q/RdBtdW5H7bvBiggUPV2tT//vK4zEkozcqdt5YOdajc
         h0e+3+IZsfWIUS1pRk0BofdYrT9o3uLw+tvug=
MIME-Version: 1.0
Date: Thu, 25 Nov 2010 02:37:04 +0100
Message-ID: <AANLkTikKF5WJHTGkTotux_G2p0xNK9WPmBgCgpJuORAd@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: hinting proposals status
From: pierre.php@gmail.com (Pierre Joye)

hi,

To avoid any possible issue or features introduced without consensus,
I'd to ask to first revert the current implementation from trunk.
There is clearly no consensus on this feature and the RFCs are either
incomplete or without actual implementations
(http://wiki.php.net/rfc/typechecking).

Then every developer involved in one of these proposals is free to
create a branch to implement or improve them. I would suggest to use
5.3 as base as it will be show clearly any kind of BC that could be
introduced.

Once a proposal is considered as ready for testing and
voting, then we can actually test its branch and take an informed
decision.

I will also proudly provide snapshots or builds for any branch at wish,
via the http://rmtools.php.net tools, like the onesones available here
(windows builds bot only for now, more coming):
http://rmtools.php.net/snaps/

By the way, this way of doing things is described in the release
process RFC, it is called a feature preview release.

Cheers,
--
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org