Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72295
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.169 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <52F20D8B.9000003@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>
 <52F20D8B.9000003@gmail.com>
Date: Thu, 6 Feb 2014 05:49:55 +0900
Message-ID: <CAGa2bXYJTP-UrVFD=PBwT=4gU0PNGQhHa=8uRusQgmTnNJ6Xgw@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1137f67c9f058004f1aee8cd
Subject: Re: [PHP-DEV] RE: RFC: expectations/assertions
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a1137f67c9f058004f1aee8cd
Content-Type: text/plain; charset=UTF-8

Hi Rowan,

On Wed, Feb 5, 2014 at 7:08 PM, Rowan Collins <rowan.collins@gmail.com>wrote:

> function foo($arg)
> {
>     assert ( (function() use ($arg) {
>         $assert_private_var = some_function();
>         return $arg == $assert_private_var;
>     })(), 'oops' );
> }
>
> Not pretty, but it would give you your local scope.
>

I agree, some thing like this is needed to call closure or pass arguments
to assert() then call.
It better than using scope. IMO.

BTW, if we would like to write down all of assert() related code inside
current assert(),
it seems this works. It still pollutes scope, though.

php > $v = 555;
php > assert(($f = function($v) {var_dump($v);return $v < 0;}) && ($f($v)));
int(555)
Warning: assert(): Assertion failed in php shell code on line 1

This may be the way to use new assert.

assert(
  ($f = function($v)
  {
    var_dump($v);return $v < 0;
  })
  &&
  ($f($v)),
  'Do not pass bad value'
);

It does not look good, but not too bad.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a1137f67c9f058004f1aee8cd--