>I'm not sure that we are talking about the same thing. Probably not. >So if socket() is removed from the core (the executable). Perl upon >noticing a socket() without a user specified use that might override >it. Will transparently make it available along with all the associated >constants. I've read these all as "remove from CORE::", which is seriously scarier. This is rather different. I don't see why anyone would care, module performance, whether for example using dbmopen autoloads Any_DBMFile or whatnot. Just try reading through the last N-thousand of these messages. Things blend together, and the overall impression is one of, well... you'll have to draw your own conclusions. --tom
- Re: RFC 146 (v1) Remove socket ... Bart Lateur
- Re: RFC 146 (v1) Remove socket ... Tom Christiansen
- 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