# hinting proposals status

- Thread: https://externals.io/message/50485
- Original archive: https://news-web.php.net/php.internals/50485
- Started by Pierre Joye on 2010-11-25T01:37:04+00:00
- Messages: 1
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #50485 — Pierre Joye — 2010-11-25T01:37:04+00:00

URL: https://externals.io/message/50485#50485

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