Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72253
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.41 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <CAGa2bXY+RsovH-CfOZntzwyY_+QEJV+Ocb=Dc69QSh9+GeS6Ug@mail.gmail.com>
References: <52EE2B66.4040005@pthreads.org> <CAGa2bXYJT+qXRXinxd_hqgPG0UfWkvCH0f6sgLyzSjM2X57j0g@mail.gmail.com>
 <CALtuQzAt_FaZwQpfJM9ed1JJSQAWb2bgP=R+hQfnVkZxZLpREw@mail.gmail.com>
 <CAGa2bXa5zON7-A6LST7yyWBrJ8ZKP7eeSSiQM-DpqNbOnrdveA@mail.gmail.com>
 <52F157BE.3020804@ajf.me> <CAGa2bXafeGSQ1X7TUsQYnnASqyBPjyT1nh=yPM9LdbW3nY3Gmg@mail.gmail.com>
 <52F15FD6.7060901@ajf.me> <CAGa2bXZvEN0KULW3MBR6y+wFKDiHOw7dXqsBeMZVYNNAXXYg2A@mail.gmail.com>
 <CAGa2bXYLkvdPXGcC=G93EKQPUBxCCKLcx-FHUK3Kt8NasD5Cvw@mail.gmail.com>
 <52F1E58F.3050105@sugarcrm.com> <CAGa2bXanYKsciVPwu30SA0HvHWDRJhv5AcG-B00+2h=fq_CUfg@mail.gmail.com>
 <52F1EF12.2050705@sugarcrm.com> <CAGa2bXYWXQUoZL20-wdRBjw98KwzbjiAKOmmmdduC_+517Pxpw@mail.gmail.com>
 <52F1F675.2000600@sugarcrm.com> <CAGa2bXY+RsovH-CfOZntzwyY_+QEJV+Ocb=Dc69QSh9+GeS6Ug@mail.gmail.com>
Date: Wed, 5 Feb 2014 18:52:50 +0900
Message-ID: <CAGa2bXb0BH0xORAwR_Ban4hCZJHcxP6bX5itEvAS-0+PGyD07Q@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>, Dmitry Stogov <dmitry@zend.com>, 
	Joe Watkins <pthreads@pthreads.org>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0160b42cb43a9c04f1a5ba8c
Subject: Re: [PHP-DEV] RE: RFC: expectations/assertions
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--089e0160b42cb43a9c04f1a5ba8c
Content-Type: text/plain; charset=UTF-8

Hi Stas and all,

On Wed, Feb 5, 2014 at 5:47 PM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:

> On Wed, Feb 5, 2014 at 5:29 PM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:
>
>> > I meant the form of the code, not assert().
>> > JavaScript uses callbacks extensively and users are used to it.
>> > PHP users are also getting used to it since the introduction of closure.
>>
>> But I mean assert(). Javascript implementations have assert() - Chrome
>> has it, Firefox has it, NodeJS has it. It does not work like you
>> propose. Doesn't it make you question your assertion that Javascript
>> users really need this?
>
>
> I think it's nice to have as it does not use variable scope/name space.
> Code related to assert() is better to hide it's existence as much as
> possible. IMO.
>
> JavaScript implementations have different APIs. Node.js has closer API.
>
> assert.throws(
>   function() {
>     throw new Error("Wrong value");
>   },
>   Error
> );
>
> while we may have
>
> assert(
>   function() {
>     // Some check here
>     return FALSE;
>  },
>  'Error'
> );
>
> I would use at least, since I don't want to assert() related code to use
> variable scope nor namespace.
>

Since I like new assert(), I thought it may help if I explain why I didn't
use assertion.
I have 2 reasons for not using old assert() at all until now.

 - Performance: couldn't accept run time overheads
 - Scope/Namespace: couldn't accept scope/namespace pollution with complex
assert.

1st one is the main reason. 2nd one, I may live with it new assert(), but I
do
not want to pollute scope/namespace if it can. It does not make sense to use
scope/namespace for assert() to me. (with complex assertion)

Before the closure introduction, I had to define function. Without
namespace, it's not
a acceptable solution at all. Even with namespace, it's far from
acceptable. Another
option is create_function(), but it's pain to write PHP code as string.
It's not acceptable
also. Closure would be acceptable, but it's not clean as it should be w/o
closure
callback support.

I cannot wait to use new assert(). If it supports closure callback, it's
PERFECT!
I'm really excited about new assert() and I wish desperately it supports
closure
callback. Please add closure callback :)

Thank you!

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--089e0160b42cb43a9c04f1a5ba8c--