Edit report at https://bugs.php.net/bug.php?id=30157&edit=1
ID: 30157 Comment by: bugs dot php at mohiva dot com Reported by: tendencies at free dot fr Summary: ftell() function does not use stream_tell() Status: Open Type: Bug Package: Streams related Operating System: * PHP Version: 5CVS-2004-09-19 (dev) Block user comment: N Private report: N New Comment: Two years later the bug is still present in 5.3.8 Previous Comments: ------------------------------------------------------------------------ [2009-02-24 17:18:11] doctorrock83 at gmail dot com Confirmed at the date of this message, the bug is still present in PHP 5.2.8, and PHP 5.3 branch. ------------------------------------------------------------------------ [2006-07-26 16:43:31] w...@php.net (PS: I got here via Bug #37096) ------------------------------------------------------------------------ [2006-07-26 16:42:25] w...@php.net I truly hope that this patch didn't get committed; it's not part of the streams design and is fundamentally redundant. I don't have time to make any further commentary than that; further analysis of the user-stream case mentioned in this bug report is required, but it certainly does not require making this kind of change to the core. ------------------------------------------------------------------------ [2005-06-16 17:22:20] tony2...@php.net >Why did you need to add tell() function to the streams internals? Because the original problem (stream_tell() is not used) looks like a bug to me. ------------------------------------------------------------------------ [2005-06-16 17:17:11] w...@php.net This tell patch (http://tony2001.phpclub.net/dev/tmp/userstreamop_tell.diff) is "wrong"; the position should be set implicitly when the stream is opened, and be updated by the streams layer when it knows that it is changed (as happens when you seek). If you need to determine the current position, you simply need to seek with a zero offset from the current position. Why did you need to add tell() function to the streams internals? ------------------------------------------------------------------------ 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
