Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58986
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CADyq6sL2zbnqcYLpc7UrctPqdK+5TYztytKCxjdVUqUidsRN2g@mail.gmail.com>
References: <CAJWj5+EwBpeMV__6SN7NbzQ0y4=RDGyg_HueU4N4AZz3Kb=CRQ@mail.gmail.com>
	<CADyq6sL2zbnqcYLpc7UrctPqdK+5TYztytKCxjdVUqUidsRN2g@mail.gmail.com>
Date: Sat, 17 Mar 2012 15:03:41 -0400
Message-ID: <CAJzDObd0M_=Qw5khGAu2fZSkgOPDLHpUz6++qkKGgWgoe_YHFQ@mail.gmail.com>
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d04479713caa5f204bb74fb9c
Subject: Re: [PHP-DEV] Scalar-type-hinting - which way is the best to go?
From: adamjonr@gmail.com (Adam Jon Richardson)

--f46d04479713caa5f204bb74fb9c
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Mar 17, 2012 at 10:37 AM, Marco Pivetta <ocramius@gmail.com> wrote:

>   Unenforced type hinting:
>   - If you have mixed types, then you just don't need type hinting. Lazy
>      devs can still avoid using it. Lazyness shouldn't really be
> encouraged, so
>      providing some kind of "backwards compatibility" just makes the
> feature
>      useless :\
>      - This is not a feature, it's just better implicit documentation for
>      methods
>

I just want to quick point out that I suggested the idea of introducing a
scalar type hint that would accept all scalars but would disallow passing
in arrays or objects. Additionally, the proposal outlined the option of
introducing aliases for the scalar hint (bool, int, float, string) which
would help developers better declare their intentions in terms of how they
expected to use the scalar type.

I don't think Nikita was referring to my idea when he referenced
"unenforced type hinting", as his examples show that passing in an object
or array would both succeed even with an int (scalar) type hint. That said,
I couldn't find a proposal suggesting a type hinting proposal that was
purely documentational, so I wanted to take the time to make sure there was
no miscommunication.

Adam

--f46d04479713caa5f204bb74fb9c--