Re: RFC: Expectations

From: Date: Mon, 21 Oct 2013 09:42:54 +0000
Subject: Re: RFC: Expectations
References: 1 2 3 4 5 6 7  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message 
On 10/21/2013 09:57 AM, Tjerk Meesters wrote:

On Mon, Oct 21, 2013 at 4:16 PM, Michael Wallner <[email protected]> wrote:


On 21 October 2013 10:13, Patrick Schaaf <[email protected]> wrote:

Am 21.10.2013 03:52 schrieb "Joe Watkins" <[email protected]>:


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

Thread (51 messages)

« previous php.internals (#69724) next »