At 10:08 PM 8/24/00 -0600, Nathan Torkington wrote: >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? Not particularly, at least not as far as I know. There's some extra cost in finding the library and loading it that you wouldn't pay if you were linked directly to it, but AFAIK that's about it. Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
- 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
- Re: RFC 146 (v1) Remove socket... David L. Nicol