Hi!
That was also the reasons why they are not present in our stream implementation. I could image something for touch (there is a FR for it afair) as it is very easy to emulate on stream where it could not work, but really not for ch*.
We have chmod now defined on all systems. However good or bad it is, I see no problems in doing the same for streams. Streams that don't have this semantics are free to not define this handler or not to support this particular option, as happens with other optional handlers - e.g., mkdir makes no sense for sockets, but that doesn't prevent mkdir from existing in streams or socket streams from working fine. If you look at the docs, you see there's even a section for streams saying what's supported and what's not by particular stream, so obviously streams not supporting some capabilities always were fine. So where's the problem?
-- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
