Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71992
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pthreads.org from 74.125.82.44 cause and error)
Message-ID: <52EE2B1D.7000307@pthreads.org>
Date: Sun, 02 Feb 2014 11:25:17 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
CC: Dmitry Stogov <dmitry@zend.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: RFC: expectations/assertions
From: pthreads@pthreads.org (Joe Watkins)

Morning Internals [, and Dmitry :)],

	I came across a reason to think about assertions again today, my 
original, pretty radical, patch was worked on by dmitry, I updated the 
RFC a while ago but allowed the conversation to die down.

	Nikita pointed this out around the same time:
	
	https://gist.github.com/krakjoe/4a2145e5a6ddc26b1dc1

	Still, there's no reason for us to have a crappy assertion api as part 
of the core just because there's a way around it(-ish) in user land.

	So, I think now is a good time to revive the discussion, the patch is 
pretty unobjectionable, and has been updated for master.

	I'd like to move this to a vote pretty swiftly, any objections ?

Cheers
Joe