At 01:00 PM 2/2/2001 -0600, Dave Rolsky wrote: >On Thu, 1 Feb 2001, Michael G Schwern wrote: > > > Problem is, its extremely difficult to figure out what module > > implements what. Sure, if you see a C<sub foo {...}> you have a > >I wasn't clear. I was thinking that somehow a module would register with >the core what interfaces it support when it is installed. Anything else >is madness (ok, my idea is madness too). Your idea's not madness--it is, in fact, what I'm looking for us to define. Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
- Re: Really auto autoloaded modules John Porter
- Re: Really auto autoloaded modules Dan Sugalski
- Re: Really auto autoloaded modules John Porter
- Re: Really auto autoloaded modules John Porter
- Re: Really auto autoloaded modules Tim Bunce
- RE: Really auto autoloaded modules Garrett Goebel
- Re: Really auto autoloaded modules Michael G Schwern
- Re: Really auto autoloaded modules John Porter
- Re: Really auto autoloaded modules John Porter
- Re: Really auto autoloaded modules Dave Rolsky
- Re: Really auto autoloaded modules Dan Sugalski
- Re: Really auto autoloaded modules Jarkko Hietaniemi
- Re: Really auto autoloaded modules James Mastros
- Re: Really auto autoloaded modules Jarkko Hietaniemi
- Re: Really auto autoloaded modules Damian Conway
- Re: Really auto autoloaded modules James Mastros
- Re: Really auto autoloaded modules Jarkko Hietaniemi
- Re: Really auto autoloaded modules John Porter
- RE: Really auto autoloaded modules Garrett Goebel
- Re: Really auto autoloaded modules Jarkko Hietaniemi
- Re: Really auto autoloaded modules John Porter