Re: RFC: Expectations

From: Date: Tue, 22 Oct 2013 19:59:01 +0000
Subject: Re: RFC: Expectations
References: 1 2 3 4 5 6 7 8 9 10 11 12 13  Groups: php.internals 
Request: Send a blank email to internals+get-69780@lists.php.net to get a copy of this message
On 10/22/2013 08:37 PM, Patrick Schaaf wrote:
Failed assertions are a sign of broken programming, not a sign to take a different code path during execution, but a sign that development must go on a little longer :) Definitely, that's not something I ever wanted to imply would be otherwise.
I have updated the RFC, there is a misleading example that I regret putting in, I have cleaned it up. I have put in a section about production time too, to clarify a few things. I hope everything is clear now ... and I hope too that I'm changing minds ... Patrick mentioned something I think is worth bringing up, that's core dumps. We can't do core dumps from Zend, there's no infrastructure to support it, and while it wouldn't require much to get a minimal one going, there is already a platform used to actually debug PHP, and it comes with well tested infrastructure. If certain people were a bit more on board, we could entertain the idea of overriding the opcode handler with xdebug and generating that coredump, or something like a coredump, I'd certainly be willing to put some effort into that and don't know how much of it is already possible with xdebug ... but no pressure, whatever .... Cheers Joe

« previous php.internals (#69780) next »