Send a blank email to [email protected] to get a copy of this message
Hi,
as the discussion phase for this RFC nears to the finish and the patch
itself is huge, I'd like to use the last chance to discuss the open
questions and concerns. Here are once more the links to the RFC (with
several updates) and the porting guide
https://wiki.php.net/rfc/size_t_and_int64http://git.php.net/?p=php-src.git;a=blob;f=compat/PECL_PORTING;hb=refs/heads/str_size_and_int64
The big open question from the previous discussion is how to handle
changed ZPP formats. The way I've suggested in the porting doc is using
ternary operator like (COMP ? "l" : "i"). Another way were to put the old
ZPP formats "lLsp" back and make them redundant to the new ones "iISP".
Both ways have their pro and contra, the second variant isn't done, but
can be done quickly.
Also one big question from the RFC which haven't been addressed is the
handling of the stale SAPIs. While porting it turned out, that more than
50% of SAPIs reference no more actively supported web servers, some of
them are even not available anymore, no packages in the current
distributions seem to exist, no chance to check if they even complaint
with PHP mainstream. The SAPIs ported so far - apache2handler, CGI, CLI,
embed, FPM, phpdbg.
Please respond also if you have any other concerns about this RFC.
The voting phase is likely to be started on Sunday, January 22.
Thanks
Anatol