>up with a better model than the C/Unix like way things are now. Having >sockets in the core makes as much sense as having the ability to open and >read disk files (early Pascal anyone?) in todays world of networked >computers. >From what Larry's said about making open work on URLs, he's in you camp. :-) >Being able to use them as easy as files would be the real goal: >open(F,"\\server.yourdomain.net:2001"); >while(<F>) > { > } >close(F); >The double slash giving a clue that this is a socket. I see only a backslash, not a pair of slashes. :-) --tom
- Re: RFC 146 (v1) Remove socket... Tom Christiansen
- Re: RFC 146 (v1) Remove socket... Uri Guttman
- Re: RFC 146 (v1) Remove socket functions from c... Joe McMahon
- Re: RFC 146 (v1) Remove socket functions fr... Dan Sugalski
- Re: RFC 146 (v1) Remove socket functions fr... Tom Christiansen
- Re: RFC 146 (v1) Remove socket function... Larry Wall
- Re: RFC 146 (v1) Remove socket functions fr... Larry Wall
- core wars (was Re: RFC 146 (v1) Remove ... Uri Guttman
- Re: core wars (was Re: RFC 146 (v1... Dan Sugalski
- RE: RFC 146 (v1) Remove socket functions from core Lipscomb, Al
- Re: RFC 146 (v1) Remove socket functions from core Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions from core Benjamin Stuhl
- Re: RFC 146 (v1) Remove socket functions from core Nick Ing-Simmons
- Re: RFC 146 (v1) Remove socket functions from c... Dan Sugalski
- Re: RFC 146 (v1) Remove socket functions fr... Bryan C . Warnock
- Re: RFC 146 (v1) Remove socket functions from core Benjamin Stuhl
- Re: RFC 146 (v1) Remove socket functions from core Dan Sugalski
- Re: RFC 146 (v1) Remove socket functions from core Nick Ing-Simmons
- RE: RFC 146 (v1) Remove socket functions from core Lipscomb, Al
- RE: RFC 146 (v1) Remove socket functions from core Fisher Mark