Edit report at https://bugs.php.net/bug.php?id=30157&edit=1
ID: 30157 Comment by: tb at bytecode dot se Reported by: tendencies at free dot fr Summary: ftell() function does not use stream_tell() Status: Closed Type: Bug Package: Streams related Operating System: * PHP Version: 5CVS-2004-09-19 (dev) Assigned To: bjori Block user comment: N Private report: N New Comment: I must say that if the documentation was updated in august 2011 then your system is really slow. If you look at the online documentation for streamWrapper::stream_tell it still says "This method is called in response to fseek() to determine the current position." Previous Comments: ------------------------------------------------------------------------ [2011-08-30 11:43:56] bj...@php.net This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. ------------------------------------------------------------------------ [2011-08-30 11:43:48] bj...@php.net Automatic comment from SVN on behalf of bjori Revision: http://svn.php.net/viewvc/?view=revision&revision=315772 Log: Fixed bug#30157, stream_tell() isn't called by ftell(), only when seeking ------------------------------------------------------------------------ [2011-08-28 22:06:32] paj...@php.net Hm, actually let move it as a to be documented instead ------------------------------------------------------------------------ [2011-08-28 22:05:36] paj...@php.net . ------------------------------------------------------------------------ [2011-08-28 22:01:39] bugs dot php at mohiva dot com I think this bug can be closed. As described by Gustavo(http://news.php.net/php.internals/54999), this is by design. And the wrong results, described in the last comments, are errors in my stream wrapper implementation. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=30157 -- Edit this bug report at https://bugs.php.net/bug.php?id=30157&edit=1