Re: Implemented fallocate() syscall in streams
| From: | Ivan Enderlin @ Hoa | Date: | Thu, 10 Jul 2014 09:18:59 +0000 |
| Subject: | Re: Implemented fallocate() syscall in streams | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-75354@lists.php.net to get a copy of this message | ||
On 10/07/2014 11:13, Julien Pauli wrote:
Cheers. -- Ivan Enderlin Developer of Hoa http://hoa-project.net/ PhD. student at DISC/Femto-ST (Vesontio) and INRIA (Cassis) http://disc.univ-fcomte.fr/ and http://www.inria.fr/ Member of HTML and WebApps Working Group of W3C http://w3.org/I admit that it would be nice for consistency, however I wonder how users will interpret the difference between ftruncate and fallocate. Users will interpret exactly what the documentation says ;-). Since PHP is a scripting language, it is just a collection of cross-platform bindings (on the top of C APIs in the case of php-src). Some bindings are just more advanced ones than others. That's all. Someone will be likely to useThe difference between ftruncate and fallocate is meaningless in userland.Iffallocateis proposed in the user-land, then it will be logical to have it in the stream wrapper API. That's it :-).fallocatesome day, for sure.