Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93790
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.175 as permitted sender)
To: Rasmus Schultz <rasmus@mindplay.dk>
References: <d9847a18-49c0-d2d0-db4e-e0d6e6685ba0@fleshgrinder.com>
 <CAESVnVoSbkT=u+agkx9mn+aqsyGv9qOo27tdbkje4qpJ2S=gFg@mail.gmail.com>
 <CADqTB_jDbkmbYEoyX-SE69ZSUu1-3aWRrJ9pYdE4vGn9acmegg@mail.gmail.com>
 <94009625-535b-d937-21b6-b454f942a82d@gmail.com>
 <CADqTB_irWb2X53L3C1ppNhxUqXL4z2+sxq7bXuWTqkYNDGZYQw@mail.gmail.com>
Cc: Sara Golemon <pollita@php.net>, PHP internals <internals@lists.php.net>
Message-ID: <ebba3ca9-0190-9dbd-9820-9f749272900c@gmail.com>
Date: Sat, 4 Jun 2016 15:36:13 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0)
 Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <CADqTB_irWb2X53L3C1ppNhxUqXL4z2+sxq7bXuWTqkYNDGZYQw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC DISCUSSION] typeof
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> The old function is actively causing confusion - the reported type-names
> aren't even inconsistent with scalar type-hints, and then you have to go
> and read the manual with some explanation about historical reasons why
> the function doesn't work like you'd expect.

Why it should match scalar types? You can't use output of this function
in a scalar type in any way.

> PHP is infamous for these surprise moments.

So let's add more of it by having multiple functions that do exactly the
same thing but name null and float differently.

> I think that gettype() should be deprecated in favor of a new function
> that actually makes sense.

If you think people would want to edit gigabytes of existing code
because you want NULL to be lowercase, you are very seriously mistaken
about the order of priority of an average PHP developer. I am sure
99.9999% of people care about all this pedantry infinitely less than
they care about their code keeping working and their development not be
impeded by things like having to read the manual each time to choose
which two of almost identical functions they need now and which of them
has null in which case.

> I think that deprecating and fixing things is long-term less confusing
> than documenting your way around legacy functions that produce
> surprising and confusing results.

I think constantly disrupting the language environment by pedantic
tweaks that add BC and cognitive load but do not actually enable
anything new, just move things around - is not only confusing, but
harmful for the whole ecosystem.

And if "NULL" really confuses you to the point you have no idea what it
means - well, really, I don't know what to say.

-- 
Stas Malyshev
smalyshev@gmail.com