Re: Re: svn: /php/php-src/ branches/PHP_5_3/ext/date/php_date.c trunk/ext/date/php_date.c
| From: | William A. Rowe Jr. | Date: | Mon, 31 Jan 2011 20:21:48 +0000 |
| Subject: | Re: Re: svn: /php/php-src/ branches/PHP_5_3/ext/date/php_date.c trunk/ext/date/php_date.c | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-51402@lists.php.net to get a copy of this message | ||
On 1/31/2011 2:04 PM, Pierre Joye wrote:
> On Mon, Jan 31, 2011 at 8:52 PM, William A. Rowe Jr.
> <wrowe@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? 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.