Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93770
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <a6f8fc9f-be2f-0f30-b0d0-8d5f34cca092@fleshgrinder.com>
References: <d9847a18-49c0-d2d0-db4e-e0d6e6685ba0@fleshgrinder.com>
 <CA+kxMuTWzqDhGqiiuLjabK7eMXev8LSrvRx48+PrzO7DxYNpBA@mail.gmail.com> <a6f8fc9f-be2f-0f30-b0d0-8d5f34cca092@fleshgrinder.com>
Date: Sat, 4 Jun 2016 18:17:46 +0200
Message-ID: <CADyq6sL72Xy9EzTE1weUbf5B1cXv75zNRy6Z6PvsQ5sB-mf9rw@mail.gmail.com>
To: PHP Internals List <internals@lists.php.net>
Cc: Dan Ackroyd <danack@basereality.com>
Content-Type: multipart/alternative; boundary=089e012294464a61190534762fd0
Subject: Re: [PHP-DEV] [RFC DISCUSSION] typeof
From: ocramius@gmail.com (Marco Pivetta)

--089e012294464a61190534762fd0
Content-Type: text/plain; charset=UTF-8

It would be beneficial to not reduce this to stringly-typed programmer
(again), as Dan mentioned.

Returning something like a ReflectionType instance (which then implements
__toString) would be much simpler, efficient and easy to use.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

On 4 June 2016 at 18:05, Fleshgrinder <php@fleshgrinder.com> wrote:

> On 6/4/2016 4:34 PM, Dan Ackroyd wrote:
> > Hello FG,
> >
> > Having a standard way to get the type of a variable, that matches the
> > name of how it appears in PHP is a good idea.
> >
> > The 'extended' parameter is not such a good idea, for various reasons
> > but mainly because it's simpler for people to call is_callable() as
> > well as typeof, rather than having to interpret the extended string to
> > tell if a string represents a callable.
> >
> > The same is true for floats; it is easier for people to call
> > is_infinite or is_nan rather than searching inside a string for
> > 'infinite' or 'invalid'.
> >
> > cheers
> > Dan
> >
>
> Hi Dan,
>
> many thanks for your feedback. This is definitely NOT the purpose of the
> extended mode, and I tried to emphasize this in the RFC. I also think it
> would be very bad to introduce anything that would compete with any of
> the existing is_* functions. It is also the reason why the strings are
> very verbose and human readable: they are meant for debug and error
> messages.
>
>   // complicated code ...
>   // error branch {{{
>
>     $type = typeof($v, true);
>     throw new Ex('Expected Foo but got ' . $type);
>
>   // }}}
>   // complicated code ...
>
> This matches the main usage -- according to my research -- of the
> existing gettype() function in userland software. :)
>
> --
> Richard "Fleshgrinder" Fussenegger
>
>

--089e012294464a61190534762fd0--