Dan Sugalski writes: > One of the current plans is for the parser to have access to a list of > functions that trigger autoloading modules. Isn't dynamic loading really slow? If they're going to incur the penalty of dynamic loading, you might as make them request that slowdown by 'use'ing the module. The alternative is that they memorize a long list of functions, some of which are slow and some of which aren't. Nat
- 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
- Re: RFC 146 (v1) Remove socket... David L. Nicol
- Re: RFC 146 (v1) Remove socket... Dan Sugalski