Re: Question about socket ext. file descriptors

Zeev Suraski writes: > ext/sockets does indeed appear to be broken; It doesn't obey the standard > PHP return value rules at all (errors are negative numbers instead of > false, resource are passed back as-is instead of as resources). > > I was actually looking at the other socket functions, fsockopen() and > friends. They're ok. > > Zeev Ah. Please to be disregarding my last post then. :) I guess sockets can be considered 'likely to change somewhat' before it becomes non-experimental, then. Which is actually the info I was after. Thanks for the explanations from both of you guys, though. Slightly different topic--is it a problem that call-time pass-by-ref is being deprecated but several functions require it in order to work? > At 15:52 29/3/2001, Andi Gutmans wrote: > >Well we were talking about the ext/socket extension and all functions > >there which create file descriptors are leaking. It's not an exception. > >Check open_listen_sock() and accept_connect(). > >You were probably looking at the fd set functions which are just > >emalloc()'ed memory. The happen to use resources but even if they hadn't > >it would be a leak which the Zend memory manager would clean up. The file > >descriptors is the real problem. > > > >Andi > > -- > Zeev Suraski <zeev@zend.com> > CTO & co-founder, Zend Technologies Ltd. > http://www.zend.com/ > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net > -- +----------------------------------------------------------------+ |Torben Wilson <torben@php.net> Adcore Finland| |http://www.coastnet.com/~torben http://www.adcore.com| |Ph: 1.604.709.0506 torben@adcore.com| +----------------------------------------------------------------+