Re: [PHP-DEV] Re: phpdbg situation in PHP-5.6

2014-10-30 Thread Bob Weinand
> Am 30.10.2014 um 19:23 schrieb Stas Malyshev : > > Hi! > >> An alternative would be just putting a few #if 0 in code >> (phpdbg_out.c where the outputting of anything is centralized) to >> make XML stuff not usable. Maybe that one is the cleanest and least >> invasive with still allowing us to

Re: [PHP-DEV] Re: phpdbg situation in PHP-5.6

2014-10-30 Thread Stas Malyshev
Hi! > An alternative would be just putting a few #if 0 in code > (phpdbg_out.c where the outputting of anything is centralized) to > make XML stuff not usable. Maybe that one is the cleanest and least > invasive with still allowing us to change the whole XML stuff. And at > the same time the norma

Re: [PHP-DEV] Re: phpdbg situation in PHP-5.6

2014-10-30 Thread Pierre Joye
On Oct 30, 2014 5:59 PM, "Bob Weinand" wrote: > To add for 3.: Issues where with what I really couldn’t think of (separate build dir on Linux…) or the issues with a JSON dep or Windows which I couldn’t test. For this part, I can get you and Joe full msdn subscription if desired.

Re: [PHP-DEV] Re: phpdbg situation in PHP-5.6

2014-10-30 Thread Remi Collet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 30/10/2014 11:59, Bob Weinand a écrit : > Also, just to point it out: Windows allows extensions to be in a > random directory, *nix does not. I’d rather change the > /acinclude.m4 to not be bound to the /ext directory, so that it > just works like