>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). Unless that's done completely transparently, you'll pretty much screw the pooch as far as "Perl is the Cliff Notes of Unix" notion. Not to mention running a very strong risk of butchering the performance. I don't understand this desire to eviscerate Perl's guts. Having everything you want just *there* is part of what's made Perl fast, fun, and successful. Good luck on preserving all three. --tom
- Re: Splitting core functions i... Grant M.
- Re: RFC 146 (v1) Remove socket functions fr... Dan Sugalski
- Re: RFC 146 (v1) Remove socket function... Nick Ing-Simmons
- Re: RFC 146 (v1) Remove socket fun... Dan Sugalski
- Re: WAP-enabled cellular furbi... Joshua N Pritikin
- Re: RFC 146 (v1) Remove socket functions from core Michael Maraist
- Re: RFC 146 (v1) Remove socket functions from core Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions from c... Bradley M. Kuhn
- Re: RFC 146 (v1) Remove socket functions fr... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions from core Stephen P. Potter
- Re: RFC 146 (v1) Remove socket functions from c... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions fr... Dan Sugalski
- Re: RFC 146 (v1) Remove socket function... Nathan Torkington
- Re: RFC 146 (v1) Remove socket fun... Dan Sugalski
- Re: RFC 146 (v1) Remove socket... Nick Ing-Simmons
- Re: RFC 146 (v1) Remove socket... Dan Sugalski
- Re: RFC 146 (v1) Remove socket... Alan Burlison
- RE: RFC 146 (v1) Remove socket... Al Lipscomb
- RE: RFC 146 (v1) Remove socket... Nick Ing-Simmons
- Re: RFC 146 (v1) Remove socket... David L. Nicol
- Re: RFC 146 (v1) Remove socket... Nick Ing-Simmons