>Remove socket functions from core Why? What is the justification? I can think of some, but you haven't given them. In general, the misplaced zealotry to strip Perl down into someting where nothing is predefined is hardly a good investment. It's not like it will make anything appreciably smaller or faster, as previous studies have already proven. There's no need to have Perl become a language with merely seven keywords and everything else requires loading a million libaries for. You have but to look at Forth or Tcl or Python for how much that is. Perl has always had a lot of functionality predefined. Why would you want to break that?? --tom
- 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