Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69724
Return-Path: <krakjoe@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 44360 invoked from network); 21 Oct 2013 09:42:58 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 21 Oct 2013 09:42:58 -0000
X-Host-Fingerprint: 80.4.21.210 cpc22-asfd3-2-0-cust209.1-2.cable.virginmedia.com  
Received: from [80.4.21.210] ([80.4.21.210:2423] helo=localhost.localdomain)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 31/FE-44908-227F4625 for <tjerk.meesters@gmail.com>; Mon, 21 Oct 2013 05:42:58 -0400
To: internals@lists.php.net,Tjerk Meesters <tjerk.meesters@gmail.com>
Message-ID: <5264F71E.6050705@php.net>
Date: Mon, 21 Oct 2013 10:42:54 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
References: <3D.BC.23638.84CA1625@pb1.pair.com> <000301cecd1b$9aa133f0$cfe39bd0$@tutteli.ch> <CAH-PCH4y5qiXyLLw8ezv1RDzq-NomghAG0ZbPm0Kve=OZspTCg@mail.gmail.com> <526488C1.8020400@php.net> <CAJ26g5T7-zbvs1JVspFkCqT+v8mn34m6XY=GhrQKgxNypEAp=A@mail.gmail.com> <CALJZF3inVJMTMdaZCPd4mRdo9z3R6u58z5GL=bRaj6X79oxDxg@mail.gmail.com> <CAHMUw2FGR0SFL71N+Lq9fOkLtp8GC2btc1iGgSMLu0mxqurYXw@mail.gmail.com>
In-Reply-To: <CAHMUw2FGR0SFL71N+Lq9fOkLtp8GC2btc1iGgSMLu0mxqurYXw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Posted-By: 80.4.21.210
Subject: Re: [PHP-DEV] RFC: Expectations
From: krakjoe@php.net (Joe Watkins)

On 10/21/2013 09:57 AM, Tjerk Meesters wrote:
> On Mon, Oct 21, 2013 at 4:16 PM, Michael Wallner <mike@php.net> wrote:
>
>> On 21 October 2013 10:13, Patrick Schaaf <bof@bof.de> wrote:
>>> Am 21.10.2013 03:52 schrieb "Joe Watkins" <krakjoe@php.net>:
>>>>
>>>> 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...
>>
>
> Since we're throwing around terms, here's another one:
>
> predicate <expr>;
>
> It should be understood by most programmers what it means (though,
> admittedly, it doesn't carry an obvious severity) and isn't used anywhere
> in the language (afaik).
>
>
>>
>>
>> --
>> Regards,
>> Mike
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>
>
I suggest we process thusly:

	We need some consensus as to whether this is actually a problem or not 
before we get lost in suggestions ...
	Should we decide it's a problem then we need to decide if using the 
keyword "expected" solves the problem ...
	Should there still be a problem we should compile a short list and get 
a consensus on it before proceeding to make necessary changes.

So first of all, can we get a quick +|-1 on:
	
	Using "expect" is a problem
	Using "expected" solves the problem

We can proceed from there I think ...

Cheers
Joe