Hi!
> a) Error handlers can (and often do) throw. E.g. it is possible to convert
> the two recoverable fatal errors that __toString() currently throws into
> exceptions and end up in the situation you describe, only with even less
> safety and more leaks. However this applies to all occurrences of
Developing the PHP runtime
Maintaining an official, bundled PHP extension
Maintaining the documentation
Translating the documentation
Maintaining php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi internals!
In a previous thread on the topic [1] I promised to create an RFC for the
soft-reservation of 'void', similar to a bunch of other reservations we
have done for PHP 7. The RFC also includes 'enum' as an additional
independent proposal, as I think this will likely be needed in 7.x. If
On Thu, Jun 25, 2015 at 3:55 PM, Johannes Schlüter
wrote:
> On Thu, 2015-06-25 at 14:52 +0200, Nikita Popov wrote:
> > However what it doesn't do, and what I wouldn't consider feasible to do,
> is
> > ensure that every single string conversion in library functions is
> > exception safe. Personall
Hi Anatol,
Anatol Belski wrote:
> Hi Christoph,
>
> Shouldn't it be only active for ODBCVER >= 0x0300 (see also the other code
> around this)?
Yes, of course. Thanks. I'll fix it ASAP.
Regards,
Christoph
> Regards
>
> Anatol
>
>> -Original Message-
>> From: Christoph Michael Bec
