Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85556
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain dancryer.com does not designate 209.85.214.174 as permitted sender)
MIME-Version: 1.0
References: <3a939905cd5a06158c9e99d8af26e596@mail.gmail.com>
In-Reply-To: <3a939905cd5a06158c9e99d8af26e596@mail.gmail.com>
Date: Mon, 30 Mar 2015 14:24:02 +0000
Message-ID: <CABoMkDZqTRMtzYkHerpgew9Zmc8kd3mwmq47HMSvx_PaMEtHzA@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e011825ecde67cd0512823b7f
Subject: Re: [PHP-DEV] Naming of 'weak' type hints
From: dan@dancryer.com (Dan Cryer)

--089e011825ecde67cd0512823b7f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

>
> We could
> also consider going for =E2=80=98lax=E2=80=99 or =E2=80=98lenient=E2=80=
=99 as the opposite of =E2=80=98strict=E2=80=99,
> although I think we can easily do without introducing a new word into the
> vocabulary here.
>

From an user perspective, I'd suggest that "lax" would potentially carry
more negative connotations than "weak." Lax implies (to me) that the engine
is being negligent in not checking the types...

Dynamic for "weak" types, and Strong for "strict" types would make the most
sense to me. :)

--089e011825ecde67cd0512823b7f--