Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72237 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14418 invoked from network); 5 Feb 2014 03:12:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Feb 2014 03:12:32 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.43 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.43 mail-la0-f43.google.com Received: from [209.85.215.43] ([209.85.215.43:53296] helo=mail-la0-f43.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DD/C0-08465-E1CA1F25 for ; Tue, 04 Feb 2014 22:12:31 -0500 Received: by mail-la0-f43.google.com with SMTP id pv20so7196229lab.16 for ; Tue, 04 Feb 2014 19:12:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=UWC5tyCZCVhs3Lgy0uz/Ru+zG88tYwBz6/0EEQnUdes=; b=G9rUhEfPTA9I61YdTtPpKFs9/XQMlI15xJ9TnTFnvH5+O6WqWyqx3lIbXPHkmAxVF4 Ol4Ihx1Q9sJBoG3AHyfIgAJgztZI6PVbR9DzTMADdDj4NLyi565cvWEemfkXedDMza8l ko+jl4962psULsq+/lFt/lEwyGLtGWzcUNL9BMDDyFsrSDCZyInh3g041HuOqYPmK5PZ 27JkMUx9OTDhRLivVMBreTslWPwD6qlLZ6AHaVaYfTTJIDcTdBZYEi++YivLit+s2Bf2 OA9d5X1hky+D+vctUS4nKtwZqVQcbsNdqx+2r/b69T2ZTnny5m+Sj53wf3PmTPdcWOF/ JReA== X-Received: by 10.112.140.202 with SMTP id ri10mr30739756lbb.9.1391569947006; Tue, 04 Feb 2014 19:12:27 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.199.37 with HTTP; Tue, 4 Feb 2014 19:11:45 -0800 (PST) In-Reply-To: References: <52EE2B66.4040005@pthreads.org> <52F157BE.3020804@ajf.me> <52F15FD6.7060901@ajf.me> Date: Wed, 5 Feb 2014 12:11:45 +0900 X-Google-Sender-Auth: fPmEfayB6qra1h1QFxtJcigYgG8 Message-ID: To: Joe Watkins Cc: PHP internals Content-Type: multipart/alternative; boundary=001a11c25dea5f1e1304f1a0206d Subject: Re: [PHP-DEV] RE: RFC: expectations/assertions From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c25dea5f1e1304f1a0206d Content-Type: text/plain; charset=UTF-8 Hi all, On Wed, Feb 5, 2014 at 7:53 AM, Yasuo Ohgaki wrote: > php > assert('function() {return FALSE;}'); > php > assert('function() {return TRUE;}'); > > It does not work, but > > php > assert(eval('function() {return FALSE;};')); > > Warning: assert(): Assertion failed in php shell code on line 1 > > so closure in eval() works. I don't see reason not to allow closure > directly. > It only seems inconsistent to me. > Added this to inconsistent behaviors RFC to track. https://wiki.php.net/rfc/inconsistent-behaviors#assert Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c25dea5f1e1304f1a0206d--