This is frustrating (and annoying). It's a simple abstraction layer so that the zend engine can efficiently parse input from arbitrary data sources, including, but not limited to, php streams.
If you told me exactly what you're trying to do, we can work together more productively. Instead, you've got some secret code that needs to do something magical with the stream; you won't tell me what that is, and you don't seem to understand that the code is the way it is, for abstraction purposes. If you would ask useful, practical questions, like "I need to be able to stat the stream and perform operations X, Y, Z; how can we implement that?", then I can help. It's a waste of time otherwise. --Wez. On Sun, 13 Mar 2005 17:13:04 +0200 (IST), Stanislav Malyshev <[EMAIL PROTECTED]> wrote: > WF>>> handlers for streams (php_stream *). I do not understand why do you use > WF>>> the same thing for FPs (once more for FILE *, not for php_stream *!) - > WF>>> provided that the only function that actually benefits from it is > WF>>> zend_stream_read and it is not overridable. > WF>> > WF>>Read the code again; the read function is assigned along with the type > WF>>and pointer. > > OK. I know it and I said twice I know it. This still does not answer my > question: why FP is converted to STREAM and is read via handler if you could > read it just fine via FP and only place where you need the handler is > zend_stream_read? > > -- > Stanislav Malyshev, Zend Products Engineer > [EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115 > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
