Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78185
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.218.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <66B7B28C-2651-4A71-AC2A-55D4C7BB3DDC@ajf.me>
References: <66B7B28C-2651-4A71-AC2A-55D4C7BB3DDC@ajf.me>
Date: Tue, 21 Oct 2014 13:14:49 +0400
Message-ID: <CA+9eiLs9j0XMbtNKSSuqTBhF-BEc1CU__3E4gOhYwuF5zF4_1g@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c30fbc693f970505eb433a
Subject: Re: [PHP-DEV] [RFC] Safe Casting Functions
From: dmitry@zend.com (Dmitry Stogov)

--001a11c30fbc693f970505eb433a
Content-Type: text/plain; charset=UTF-8

Both, the idea and implementation look fine.

Personally, I hate the existing type conversion rules, and I would like to
use something like this by default (may be with exception for
null/false/true handling), but it may be a big compatibility break, so
introducing to_int() is better than nothing.

some notes:
- it's probably make sense to implement these function as a new opcode(s)
in VM
- in case of conversion failure it's better to throw exception (to_int()
returning FALSE is a pain).

Thanks. Dmitry.

On Tue, Oct 21, 2014 at 2:57 AM, Andrea Faulds <ajf@ajf.me> wrote:

> Good evening,
>
> I am presenting a new RFC to add a set of three functions to do validated
> casts for scalar types:
>
> https://wiki.php.net/rfc/safe_cast
>
> Please read it.
>
> Thanks!
> --
> Andrea Faulds
> http://ajf.me/
>
>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a11c30fbc693f970505eb433a--