RE: [PHP-DEV] [RFC] Safe Casting Functions
| From: | Zeev Suraski | Date: | Wed, 22 Oct 2014 22:34:13 +0000 |
| Subject: | RE: [PHP-DEV] [RFC] Safe Casting Functions | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-78257@lists.php.net to get a copy of this message | ||
> -----Original Message-----
> From: Andrey Andreev [mailto:narf@devilix.net]
> Sent: Thursday, October 23, 2014 1:15 AM
> To: Zeev Suraski
> Cc: Andrea Faulds; Stas Malyshev; Dmitry Stogov; PHP Internals
> Subject: Re: [PHP-DEV] [RFC] Safe Casting Functions
>
> > While it doesn't explicitly say so, it's clear that one of the goals
> > of the RFC is make it easier for a 'strict typing' RFC to be accepted
> > in the future. This is a clear indication this constitutes a
> > fundamental
> change to the core language.
>
> I'd argue that it has the exact opposite goal - to be able to say "use
> to_string(), to_int(), etc; we don't need strict type hinting".
You may be right, I may have misinterpreted the rationale - but I think the
consequences are still the same. If this (in the eyes of the author) undoes
the need for a feature as fundamental as strict typing, how can it be just a
bunch of simple functions?
Zeev