Re: RFC 146 (v1) Remove socket functions from core

[Stephen P. Potter]

Lightning flashed, thunder crashed and "Michael Maraist" <maraism@ironhilltechn
ology.com> whispered:
| >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.

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).

-spp