At 10:26 AM 8/24/00 -0600, Tom Christiansen wrote: > >Remove socket functions from core > >Why? What is the justification? I can think of some, but you >haven't given them. There are a number of good reasons to do this from an internals standpoint, enough that I'd like to do it. From an externals standpoint, though... I've yet to hear a compelling reason to require a "use thingies;" to yank 'em in. That being the case, I've a scheme that makes them external as far as the internals are concerned, but internal as far as the externals are concerned. Best of both worlds, more or less. Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
- 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
- Re: RFC 146 (v1) Remove socket f... 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