On Fri, Apr 12, 2013 at 10:53 AM, Julien Pauli wrote:
> On Wed, Apr 10, 2013 at 7:14 PM, Dmitry Stogov wrote:
>
> > Hi,
> >
> > 1) I didn't get why do we need fprintf("Loaded/Unloaded extension").
> It'll
> > break all the tests in DEBUG mode
> >
> > 2) zend_error() may work through SAPI handler
On Wed, Apr 10, 2013 at 7:14 PM, Dmitry Stogov wrote:
> Hi,
>
> 1) I didn't get why do we need fprintf("Loaded/Unloaded extension"). It'll
> break all the tests in DEBUG mode
>
> 2) zend_error() may work through SAPI handler (e.g. for FastCGI sapi it
> may try to send error message to WebServer w
On Wed, Apr 10, 2013 at 7:14 PM, Dmitry Stogov wrote:
> Hi,
>
> 1) I didn't get why do we need fprintf("Loaded/Unloaded extension"). It'll
> break all the tests in DEBUG mode
>
Great catch
>
> 2) zend_error() may work through SAPI handler (e.g. for FastCGI sapi it
> may try to send error messa
Hi,
1) I didn't get why do we need fprintf("Loaded/Unloaded extension"). It'll
break all the tests in DEBUG mode
2) zend_error() may work through SAPI handler (e.g. for FastCGI sapi it may
try to send error message to WebServer while request context is not
initialized yet). I think it must work n
hi,
On Wed, Apr 10, 2013 at 6:50 PM, Julien Pauli wrote:
> Hi all,
>
> Here are two branches that improve extension loading mechanisms and remove
> dusty old features not used any more.
>
> No BC or nothing, though perhaps some Windows support tricks to add ?
>
> Thoughts ?
>
> https://github.com
