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 now, but should be double checked.
Thanks. Dmitry.
On Wed, Apr 10, 2013 at 8:57 PM, Pierre Joye <pierre....@gmail.com> wrote:
> hi,
>
> On Wed, Apr 10, 2013 at 6:50 PM, Julien Pauli <jpa...@php.net> 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/jpauli/php-src/extensions_improvements<
> https://github.com/jpauli/php-src/compare/extensions_improvements>
> >
> > https://github.com/jpauli/php-src/tree/remove_old_php4_dl
>
> I'm not sure about the zend_error usage, I remember some issues about
> it (not always initialized and similar issues). Dmitry, do you
> remember why we used fprintf there? :)
>
> Cheers,
> --
> Pierre
>
> @pierrejoye
>
