On Mon, 3 Feb 2014, Joe Watkins wrote:
> While you can avoid some overhead in userland, you cannot remove the
> overhead completely; a good assertion API should have no impact on
> production, none, it should require no boilerplate code to make sane
> use of it, at all, since it is meant to be a core feature.
I think Stas' main objection was the inconsistencies that the "new
assert" method introduces. And I have to agree with that there. It
shouldn't depend on whether you use a string or not how the
construct/function changes code execution and exception throwing.
cheers,
Derick
--
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug
Posted with an email client that doesn't mangle email: alpine