Nathan Torkington wrote: > > moving getprotobyname() > to a module isn't the same as moving open(). And it can be transparent, if it isn't already. Why does perl need to be monolithic? I thought I selcted to build as shared libraries, splitting that into several shared libraries might be entirely painless. So if my program has getprotobyname in it clarifying that token will take a moment, but then all the other weird socket calls will be there to use. How about automatic library search before syntax error? -- David Nicol 816.235.1187 [EMAIL PROTECTED] safety first: Republicans for Nader in 2000
- RFC 146 (v1) Remove socket functions from core Perl6 RFC Librarian
- Re: RFC 146 (v1) Remove socket functions from cor... Jarkko Hietaniemi
- Re: RFC 146 (v1) Remove socket functions from cor... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions from... Dan Sugalski
- Re: RFC 146 (v1) Remove socket functions ... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functi... Nathan Torkington
- Splitting core functions into mu... David L. Nicol
- Splitting core functions int... Alan Burlison
- Re: Splitting core funct... Grant M.
- Re: RFC 146 (v1) Remove socket functi... Dan Sugalski
- Re: RFC 146 (v1) Remove socket f... Nick Ing-Simmons
- Re: RFC 146 (v1) Remove sock... Dan Sugalski
- Re: WAP-enabled cellular... Joshua N Pritikin
- Re: RFC 146 (v1) Remove socket functions from cor... Michael Maraist
- Re: RFC 146 (v1) Remove socket functions from... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions ... Bradley M. Kuhn
- Re: RFC 146 (v1) Remove socket functi... Tom Christiansen