On Sun, October 5, 2014 21:32, Anatol Belski wrote:
Hi Dmitry,
On Wed, October 1, 2014 08:01, Dmitry Stogov wrote:
Hi Anatol,
I know, TSRM uses TLS APIs internally.
In my opinion, the simplest (and probably efficient) way to get rid of
TSRMLS_DC arguments and TSRMLS_FETCH calls,
Hi Nikita,
On Sun, October 5, 2014 23:18, Nikita Popov wrote:
On Thu, Sep 18, 2014 at 5:14 PM, Anatol Belski a...@php.net wrote:
Commit:761e347b7526b18b9901ebf3d906b52a21fc9c4b
Author:Anatol Belski a...@php.net Thu, 18 Sep 2014 17:11:48
+0200
Parents:
Hi internals!
During the PHP 5.6 development cycle I have proposed an RFC [1] that
suggested the use of exceptions instead of fatal errors in the engine. At
the time the proposal was declined, because the change was judged too
intrusive for a minor version.
As such I'm re-proposing this RFC for
Hi Nikita,
On 06 Oct 2014, at 23:53, Nikita Popov nikita@gmail.com wrote:
[...]
As such I'm re-proposing this RFC for inclusion in PHP 7:
https://wiki.php.net/rfc/engine_exceptions_for_php7
The RFC text is essentially the same as previously, with the primary
difference being that
Hi!
As such I'm re-proposing this RFC for inclusion in PHP 7:
https://wiki.php.net/rfc/engine_exceptions_for_php7
The RFC text is essentially the same as previously, with the primary
difference being that parse errors are now converted to exceptions as well.
This was previously not
