I would actually further this sort of activity. I admire micro-kernel-type systems. C and Java give you no functions out of the box. Keywords are just that, keywords. I believe python is like this as well. The idea being that everything has to come from a module.. This limits how much a new developer has to learn, and it doesn't pollute the global name-space pool. Though I would advocate OO interfaces to everything, I'm sure that it would defeat a lot of perl's flexibilty, and so I'd support the simple Exporter method. >From this, socket, and virtually all IPC methods should go the wayside. This includes pipes, shell environment ops ( the get and set functions ), and even the file-io (open, close, and possibly even printf, sprintf). At this point, it gets a little hairy, since arguably, everybody wants print and <>. I would suppose that most want open as well. My personal taste is to use IO::File, but that's just me. Since these are just hooks into standard C libraries, I don't think that they really take up any room. But it is hard to justify keeping some of these less used features while taking out others (like FORMAT). -Michael
- Re: RFC 146 (v1) Remove socket functions from core Dan Sugalski
- Re: RFC 146 (v1) Remove socket functions from c... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions fr... Nathan Torkington
- Re: RFC 146 (v1) Remove socket function... David L. Nicol
- Splitting core functions into mult... Alan Burlison
- 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