On Wed, May 14, 2014 at 7:13 PM, Andrea Faulds <ajf@ajf.me> wrote:
>
> On 14 May 2014, at 18:10, Andrey Hristov <php@hristov.com> wrote:
>
> > This is purely academical. And the standard library has to support
> everything, it's the standard library. PHP is on its own, and if an
> addition is of little use to the most of the developers/scripts, why the
> heck it should be in/the default.
> > A good solution is to typedef a php_size_t, leave it to uint32_t and for
> those, who need more than 4GB in strings and elements they can just build
> with size_t as definition. Offer the choice, don't force.
>
> It is not just “purely academic”. Here, let me quote Pierre (in 'Re:
> [PHP-DEV] [VOTE] [RFC] 64 bit platform improvements for string length and
> integer’, just now) quoting Anthony:
>
I'm fairly sure than anybody reading this thread will also read the other,
so there is no reason to copypaste the mail.
If you think it is important, you can quote the relevant parts, or link to
the mail if you want to refer the whole thing.
Other than that, I'm not sure that you understood what Andrey wrote, his
idea would allow to use the size_t types, but it would be a build-time
opt-in feature.
Personally I don't like the idea, as we would have to support both types,
and as this also effects the userland (max length of strings, integer size
on windows, etc.) it would be a heavy debugging/maintenance burden.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu