For the benefit of everyone, this is all from January. Dmitry's,
Stas's and Nikita's positions in the actual patch in question can be
found on this thread.
Sent from my mobile
> On 17 במאי 2014, at 14:00, Anatol Belski <anatol.php@belski.net> wrote:
>
> Hi,
>
> from the previous episodes
>
> Dmitry
> http://grokbase.com/p/php/php-internals/141qd2k0ct/php-dev-rfc-64-bit-platform-improvements-for-string-length-and-integer
> "After some thoughts I think that usage of "size_t" is a good thing for
> the future support of X32 ABI."
>
> Stas
> http://grokbase.com/p/php/php-internals/1421be3ywy/php-dev-vote-64-bit-platform-improvements-for-string-length-and-integer
> " I can't speak for others but I can speak for myself in saying
> that these concerns are not just kicking the can down the road in hope
> that eventually this patch dies off. "
>
> Nikita:
> http://www.serverphorums.com/read.php?7,862033,862730#msg-862730
> "I fully support merging this into master, as the first change for PHP
> 6."
>
> That's pretty sad guys. Applause for playing me for a fool (well, probably
> not only me). On the other hand, I'd be honored to be as stupid as that
> old farts from ANSI who wrote the specs.
>
> Why can't you just work together instead of looking for a hair in the soup?
>
> Best regards
>
> Anatol
>
>
>> On Wed, May 14, 2014 21:48, Dmitry Stogov wrote:
>> On Wed, May 14, 2014 at 11:39 PM, Lester Caine <lester@lsces.co.uk>
>> wrote:
>>
>>
>>> On 14/05/14 10:24, Dmitry Stogov wrote:
>>>
>>>
>>>> Ah, you are on windows and lack 64-bit IS_LONG.
>>>> This is the part of the patch that should be accepted.
>>>> I mentioned it on original email.
>>> Not used windows for a number of years. 64 bit builds on Linux ...
>>
>>
>> then you already have 64-bit long, or do I miss something?
>>
>>
>>>
>>>
>>> The "bad" thing that this patch did, it changed all C data structures
>>> to
>>>> use 64-bit string lengths and it means that each such data sructure
>>>> would take more memory. Even zend_op becames bigger and as it's used
>>>> for VM byte-code representation you may just multiply the difference
>>>> to number of opcodes in application (that might be millions).
>>> Actually I do agree that this may not be ideal ...
>>>
>>>
>>>
>>> Unfortunately, phpng don't support firebird yet and it's not in our
>>>
>>>> priority list.
>>> Then there is no way that I can get involved at the present time :)
>>
>>
>> may be help in porting ext/interbase and ext/pdo_firebird :)
>>
>> I really don't know a lot about Firebird and afraid even proper
>> configuration might take us significant time.
>>
>> Thanks. Dmitry.
>>
>>
>>
>>>
>>>
>>> --
>>> Lester Caine - G8HFL
>>> -----------------------------
>>> Contact - http://lsces.co.uk/wiki/?page=contact
>>> L.S.Caine Electronic Services - http://lsces.co.uk
>>> EnquirySolve - http://enquirysolve.com/
>>> Model Engineers Digital Workshop - http://medw.co.uk
>>> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
>>>
>>>
>>> --
>>> PHP Internals - PHP Runtime Development Mailing List
>>> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>