Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85562
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.20 as permitted sender)
Message-ID: <55197A0E.8050203@gmx.de>
Date: Mon, 30 Mar 2015 18:30:06 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Zeev Suraski <zeev@zend.com>, PHP internals <internals@lists.php.net>
References: <3a939905cd5a06158c9e99d8af26e596@mail.gmail.com>
In-Reply-To: <3a939905cd5a06158c9e99d8af26e596@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: Naming of 'weak' type hints
From: cmbecker69@gmx.de (Christoph Becker)

Zeev Suraski wrote:

> One thing that I think we should change is how we refer to the ‘weak’ type
> hints.  The word ‘weak’ has a negative ring to it, and considering this is
> how the language behaves across the board it’s a pretty bad name for this
> feature.

> Personally I think we should go for ‘dynamic’ when we document it, as this
> is the common way to refer to this behavior (dynamic languages).  We could
> also consider going for ‘lax’ or ‘lenient’ as the opposite of ‘strict’,
> although I think we can easily do without introducing a new word into the
> vocabulary here.

It appears to me that all of these suggestions may hide the fact that
the arguments are converted to the hinted types.  So perhaps "converting
type hints" might be a good name.

Then again, the respective declare directive is called "strict_types",
so maybe it's best to speak of "non-strict type hints".

-- 
Christoph M. Becker