On Fri, January 10, 2014 20:32, Anatol Belski wrote:
> Hi Kalle,
>
>
> On Fri, January 10, 2014 19:29, Kalle Sommer Nielsen wrote:
>
>> Hi Anatol
>>
>>
>>
>> 2014/1/10 Anatol Belski <ab@php.net>:
>>
>>
>>> Hi,
>>>
>>>
>>>
>>> https://wiki.php.net/rfc/size_t_and_int64
>>>
>>>
>>
>> I absolutely love the work, time and effort you have put in to this
>> branch, I've been following it closely on the sideline. There is one
>> thing I'm wondering about, maybe I skipped through some of the
>> sections too fast in the RFC, but what about API BC? I know you propose
>> it for PHP6, but are there gonna be any macros or other helpers for
>> extension developers to ease the use of #ifdefs, I realize things like
>> the parameter parsing one is gonna be tough, but just as a general
>> thought, I think Derick was asking something like this not too
>> long ago?
>>
> thanks for the good words :)
>
> The short answer is: yes. I gonna start with that probably right as next.
> In plan is the tool for any possible automatic replacements and the
> header(s) for backward compatibility. That will be a big ease for the first
> step, though it can of course not replace the manual porting. Parameter
> parsing is one of the cracky points, but more it will be about the
> extension code adoption. Especially size_t usage, while being trivial,
> might get one in a muddle. I personally needed 1-2 hours to habituate
> size_t, so it works.
>
Ah, btw it is on the RFC, a couple of sentences under "Migration path for
PECL extensions".
Anatol