On Thu, 24 Aug 2000, Stephen P. Potter wrote: > I have several RFCs I need to write about removing certain functionality > out of the core (math functions, IPC, networking, "user"). I don't want to > go too overboard. I don't know that we want to go so far as to remove > printing and such. It might be nice to generalize some functions (like the > discussion with open() that happened awhile back). Hard things should be easy, easy things should be trivial. We should try to keep the stuff that is commonly used in the core (excluding OS dependent stuff, perhaps? Non-Unix folks don't see the use for getpwent(), for instance). In my opinion, Perl6 should still be a language in which it is easy to write powerful and useful programs on the command line. --- Joe M.
- Re: RFC 146 (v1) Remove socket ... Nick Ing-Simmons
- Re: RFC 146 (v1) Remove socket ... Dan Sugalski
- Re: RFC 146 (v1) Remove socket func... David Corbin
- Re: RFC 146 (v1) Remove socket ... Tom Christiansen
- What makes Perl Perl? David Corbin
- Re: What makes Perl Perl? David L. Nicol
- Re: RFC 146 (v1) Remove socket func... Chaim Frenkel
- Re: RFC 146 (v1) Remove socket ... Dan Sugalski
- Re: RFC 146 (v1) Remove socket ... Tom Christiansen
- Re: RFC 146 (v1) Remove socket ... Uri Guttman
- Re: RFC 146 (v1) Remove socket functions from co... Joe McMahon
- Re: RFC 146 (v1) Remove socket functions fro... Dan Sugalski
- Re: RFC 146 (v1) Remove socket functions fro... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions... Larry Wall
- Re: RFC 146 (v1) Remove socket functions fro... Larry Wall
- core wars (was Re: RFC 146 (v1) Remove s... 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