On Mon, Jan 31, 2011 at 9:21 PM, William A. Rowe Jr. <wr...@rowe-clan.net> wrote: > On 1/31/2011 2:04 PM, Pierre Joye wrote: >> On Mon, Jan 31, 2011 at 8:52 PM, William A. Rowe Jr. >> <wr...@rowe-clan.net> wrote: >> >>> Which I think we agree with, but you answer is a non sequitur, if you are >>> defining the 'next right solution', why deploy the n-1 build environment? >> >> I did not refer to the next right solution but the current and actual >> right solution, for PHP 5.3. We did not decide yet what to do with 5.3 >> but as trunk builds just fine for 9 or 10, that's not a big deal yet. >> I will post more on that in the next weeks. x64 support may also >> affect the choice. But I fear that to make our code base x64 friendly >> on windows (and consequently cleaner on other platforms) will require >> way too much political debate like this one > > Political?
yes, see the origin of this thread. > No, what it will require is for all the dependent libraries > to build and function properly on a 64P architecture; the vast majority > of PHP's libraries are now 64LP or 64ILP safe, but there is still a ton > of legacy code expecting void *vp = (void*)lval; and long lval = (long)vp > sorts of foolishness to work :( That will be no small challenge. To port the libraries when necessary is the smallest issue for me (so far most of them worked, last was ssh2 and we fixed the crash recently, latest pgsql supports win64 too, for example :). To argue about each commit in php-src because "it works for me with gcc so don't change it" is what will kill all the possible fun. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
