Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69736 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6702 invoked from network); 21 Oct 2013 20:36:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Oct 2013 20:36:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=rparker@yamiko.org; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rparker@yamiko.org; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain yamiko.org does not designate 173.247.247.239 as permitted sender) X-PHP-List-Original-Sender: rparker@yamiko.org X-Host-Fingerprint: 173.247.247.239 biz136.inmotionhosting.com Received: from [173.247.247.239] ([173.247.247.239:34756] helo=biz136.inmotionhosting.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5F/48-60242-C3095625 for ; Mon, 21 Oct 2013 16:36:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=yamiko.org; s=default; h=Message-ID:References:In-Reply-To:Subject:To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version; bh=cL0FYqXMGa/mON8H3L6Sy9jEZn8IM+T4hcQxm2v+k5M=; b=NIPhnXx1VU0Xa7m+ZiDqP8b5YBKjZPISWhPUchUTMLO6+L8/DO6tjVsWWxh5SA/Rr68TDLyw5xgxn27sXsVu+6ypm0hx2z9zj6cA7bATraNH9j7orqhfXxZdz9wQVB7EVn6KvzoN0HV9STpMnFNiFg/KtLBhPA+0cqK/YGYStAw=; Received: from localhost ([127.0.0.1]:39685 helo=secure136.inmotionhosting.com) by biz136.inmotionhosting.com with esmtpa (Exim 4.80) (envelope-from ) id 1VYMCr-00074C-0F for internals@lists.php.net; Mon, 21 Oct 2013 13:36:09 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 21 Oct 2013 13:36:03 -0700 To: In-Reply-To: <5264E3DC.7080603@php.net> References: <3D.BC.23638.84CA1625@pb1.pair.com> <000301cecd1b$9aa133f0$cfe39bd0$@tutteli.ch> <526488C1.8020400@php.net> <5264E3DC.7080603@php.net> Message-ID: <738f83906a93f9c499827d0d31047b28@yamiko.org> X-Sender: rparker@yamiko.org User-Agent: Roundcube Webmail/0.8.5 X-OutGoing-Spam-Status: No, score=-2.9 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - biz136.inmotionhosting.com X-AntiAbuse: Original Domain - lists.php.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - yamiko.org X-Get-Message-Sender-Via: biz136.inmotionhosting.com: authenticated_id: rparker@yamiko.org Subject: Re: [PHP-DEV] RFC: Expectations From: rparker@yamiko.org On 2013-10-21 01:20, Joe Watkins wrote: > On 10/21/2013 09:16 AM, Michael Wallner wrote: >> On 21 October 2013 10:13, Patrick Schaaf wrote: >>> Am 21.10.2013 03:52 schrieb "Joe Watkins" : >>>> >>>> So looks like we need a new name ?? Ideas ?? >>> >>> abstract EXPRESSION >> >> wat? >> >> >>> abstract is already a keyword, so no BC. >>> >>> abstract is not concrete so alludes a bit to the >>> might-be-or-might-not-be-checked nature of the test >>> >>> abstract is the name for the "short summary" intro part of >>> scientific >>> papers, and these conditions are kind of a summary of what is known >>> (preconditions) and concluded (postconditions). >> >> Ah, ok well. I'd rather go for expected() or except() then... >> >> > Expected appears to be the most suitable solution suggested so far ... > > I was following along with the abstract suggestion, I thought that > was pretty well thought out, but a bit hard to explain why we are > re-using the abstract keyword for something that is completely > unrelated to abstract classes all the same ... > > So for those that see the problem does Expected work around it ?? > > Cheers > Joe This proposal sounds a lot like exceptions to me or am I missing something :/ Could we do something like throw new expectation($expects, $message);