At 02:08 PM 2/2/2001 -0800, Nathan Wiger wrote:
>Dave Rolsky wrote:
> >
> > That's what I was thinking. The point is that the module identifies the
> > services it provides. Multiple modules may provide overlapping sets of
> > services. Modules could also be somehow ranked (memory usage and speed
> > come to mind).
> >
> > Then I could put this into my module:
> >
> > needs CGI;
> > needs URI;
> > needs HTML::Output;
> > needs HTTP;
>
>First off, let me say that I like the autoloading idea, and tying it in
>with class contracts, and all that in theory.
>
>However, it also seems that this is getting *really* complicated really
>quickly.
I'd agree. I was picturing the file the parser used reading something like:
socket|Socket|1.0|gt
to indicate that seeing a socket sub loaded in Socket v1.0 or higher, with
some corresponding way in the Socket module to add that line into the
parser's magic file.
Folks seem to be getting a little out of hand, but it might get something
useful, so I'm hesitant to stop things quite yet.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
