Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83990
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.50 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <3d639901ae85227b219e7ee59b3140fe@mail.gmail.com>
References: <BAY178-W418C61DF38879BED71640EDE140@phx.gbl> <3d639901ae85227b219e7ee59b3140fe@mail.gmail.com>
Date: Fri, 27 Feb 2015 19:25:14 +0900
Message-ID: <CAGa2bXZqzR3_4fZh_DcAsLVWLmsL34F-DE69eGv2MW_AhNhmQg@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: Theodore Brown <theodorejb@outlook.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c1169a2a4d7c05100f4b89
Subject: Re: [PHP-DEV] A different user perspective on scalar type declarations
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11c1169a2a4d7c05100f4b89
Content-Type: text/plain; charset=UTF-8

Hi Zeev,

On Fri, Feb 27, 2015 at 2:48 AM, Zeev Suraski <zeev@zend.com> wrote:

> You may have a point there.  As Francois said, he was in favor of allowing
> leading and trailing spaces.  I'll definitely reconsider.
>

If we consider existing code, leading/trailing spaces may need to be
allowed.
Without considering compatibility issues, leading/trailing spaces should be
validated or removed by user input validation/filter code in the first
place.

I think many users use "$" for the end of string data for regex, but it
includes
newline. To be precise, "\z" should be used for both PCRE and mbregex.

http://perldoc.perl.org/perlre.html

Trailing newline is invalid. Leading/trailing spaces may be considered as
the
same invalid data to be strict.

This is what I thought for this.
I don't have strong opinion.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11c1169a2a4d7c05100f4b89--