Re: Large file support for PHP
| From: | Wez Furlong | Date: | Tue, 16 Oct 2007 14:37:57 +0000 |
| Subject: | Re: Large file support for PHP | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-32816@lists.php.net to get a copy of this message | ||
On Oct 16, 2007, at 2:44 AM, sean finney wrote:
i would suggest that anywhere where one is doing something with a size or offset and not using the posix size_t/off_t types should get such changes. and like i said, i don't see the motivation behind this extra step of returning the size in double form if it's bigger than LONG_MAX.PHP's native integer type is long, how else are you going to relay numbers longer than a long back to the script without rewriting the engine to add additional integer types, which is a massive changeset?
i don't think switching from long/int -> size_t is a problem in the scope of function internal variables. the only place where you need to worry about this is in headers/structs/function declarations that are exported to the API/ABI.Or just bump our API number(s) and "not worry about it", since the module loading code will refuse to load an incompatible module. PHP 5.3 is an ideal point to make this kind of change, as I've already stated. --Wez.