Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94640
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <c8fa44b6-c7e9-c4ae-ce03-474c96ead2f6@gmail.com>
References: <7716d180-2365-efc9-e9b3-9fe0998e273b@fleshgrinder.com>
 <CAF+90c_F_YgpsCkfAqZdj2VzeiUGRqUmmguGhHkf-9Tdrvt5Sg@mail.gmail.com> <c8fa44b6-c7e9-c4ae-ce03-474c96ead2f6@gmail.com>
Date: Fri, 22 Jul 2016 22:21:19 +0200
Message-ID: <CAF+90c_4S7XyhhJ1C8iRjGFxnHUMrfNHMUni+0rBOBwKQHg2_g@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c1461fa735b1305383f2dc4
Subject: Re: [PHP-DEV] [RFC] [Vote] var_info
From: nikita.ppv@gmail.com (Nikita Popov)

--94eb2c1461fa735b1305383f2dc4
Content-Type: text/plain; charset=UTF-8

On Sat, Jul 9, 2016 at 12:19 AM, Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> Hi!
>
> > Lastly, I'll just leave this list of type-related improvements I'd
> actually
> > like to see:
> >  * Make is_object() return true for IncompleteClass. This is just
> > ridiculous. I care zero about the theoretical BC impact.
>
> I have no idea why it doesn't do so. I'll try to dig up when it was made
> so and see if there's some explanation.
>
> >  * Make gettype() return 'resource (unknown type)'  instead of just
> > 'unknown type' for closed resources. This makes the output clear while
> > still leaving the closed resource distinction.
>
> That makes total sense. And BC impact is rather minimal given that
> closed resources are useless.
>

I've created PRs for both of these:

gettype() on closed resources: https://github.com/php/php-src/pull/2022
is_object() on Incomplete_Class: https://github.com/php/php-src/pull/2023

Unless there are objections from core devs I'll apply both in a few days.

Nikita


>  * Normalize error message. IIRC currently our type error messages are
> > really weird, in that they use terms like "integer" which are not
> actually
> > valid type hints (or have different meaning). Fixing this doesn't even
> need
> > a proposal, just a PR.
>
> Right. But ensure tests are fixed, that's probably where one has to
> spend some time on cleaning it up.
>
> --
> Stas Malyshev
> smalyshev@gmail.com
>

--94eb2c1461fa735b1305383f2dc4--