Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78161
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.182 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 02:16:24 +0300
Message-ID: <CANu1ninkUHNUfOKahTB1zphFgES_LW180aiOiezdWgkzQUreFQ@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c26b424a62b60505e2e77d
Subject: Re: [PHP-DEV] [RFC] Safe Casting Functions
From: hkdobrev@gmail.com (Haralan Dobrev)

--001a11c26b424a62b60505e2e77d
Content-Type: text/plain; charset=UTF-8

In general I like this RFC.

I don't see why to_string would not accept and cast integers and floats to
strings. And even if there is a valid reason it is not mentioned.

If this gets accepted you should consider the naming in the user
documentation. Beginners should not consider these functions "safe" as in
"security", but only "safe" as in "no data loss".
On Oct 21, 2014 1:58 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
>
>

--001a11c26b424a62b60505e2e77d--