Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82849
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54E20027.1000809@gmail.com>
References: <82D0FEAC-4B86-4589-A21B-51A9E8795D8A@ajf.me> <003e01d04976$77e0bc90$67a235b0$@php.net>
 <54E1CF5C.1050001@gmail.com> <00c801d049e3$f7b6f1b0$e724d510$@php.net> <54E20027.1000809@gmail.com>
Date: Mon, 16 Feb 2015 16:46:55 +0200
Message-ID: <CAL0xaBHtO3Tw3gJkV0gvRDyut7M=dNvQun9g+kSpZxQ1mJVGSA@mail.gmail.com>
To: Jefferson Gonzalez <jgmdev@gmail.com>
Cc: Rowan Collins <rowan.collins@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113d60848d3e71050f35a9d7
Subject: Re: [PHP-DEV] I quit.
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--001a113d60848d3e71050f35a9d7
Content-Type: text/plain; charset=UTF-8

The 0.1 RFC version was mentioned a lot as a good compromise by many people
and had major support.
Maybe someone competent could pick it up, make necessary adjustments that
where required and let people vote on it? Start with small steps - get the
weak type hints into the language first, see how it gets used and then we
can always add strict type hints if there is a need/desire to do that.

That way we finally get type hints into the language, and those wanting the
strict variety have all the opportunities in the world to add them at a
later release with proper discussion and development time.

Thanks,
Arvids.

--001a113d60848d3e71050f35a9d7--