Benjamin Stuhl <[EMAIL PROTECTED]> writes: > >There's also the issue that _each_ symbol must be requested >manually and stored somewhere (in a MT-safe manner, of >course), That is not the right way to do it. (I have seen the Tcl loader and I think it is ugly.) The loadable would export _one_ symbol - that of a table of functions. (Which is what DBI and Tk do and have since perl5.001m or so...) -- Nick Ing-Simmons
- core wars (was Re: RFC 146 (v1) Remove ... 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
- Re: RFC 146 (v1) Remove socket functions from core Benjamin Stuhl
- Re: RFC 146 (v1) Remove socket functions from core Nick Ing-Simmons
- Re: RFC 146 (v1) Remove socket functions from c... Dan Sugalski
- Re: RFC 146 (v1) Remove socket functions fr... Bryan C . Warnock
- Re: RFC 146 (v1) Remove socket functions from core Benjamin Stuhl
- Re: RFC 146 (v1) Remove socket functions from core Dan Sugalski
- RE: RFC 146 (v1) Remove socket functions from core Nick Ing-Simmons
- RE: RFC 146 (v1) Remove socket functions from core Lipscomb, Al
- RE: RFC 146 (v1) Remove socket functions from core Fisher Mark
- Re: RFC 146 (v1) Remove socket functions from core Larry Wall
- how small is small? (was Re: RFC 146 (v1) Remove so... Bradley M. Kuhn
- RE: RFC 146 (v1) Remove socket functions from core Lipscomb, Al
- Re: RFC 146 (v1) Remove socket functions from core Tom Christiansen
- RE: RFC 146 (v1) Remove socket functions from core Lipscomb, Al
- RE: RFC 146 (v1) Remove socket functions from core Fisher Mark
- RE: RFC 146 (v1) Remove socket functions from core Nick Ing-Simmons
- Re: RFC 146 (v1) Remove socket functions from core Tom Christiansen