Damian Conway wrote: > > > >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 > > I think this is the way to go. I'd suggest that the syntax be easier for > humans (or at least JAPHs ;-) to intepret, and that the condition be > fully generalizable. Something like: > > autouse Socket::socket { $Socket::VERSION >= 1.0 } > autouse Text::Reform::format { 1 } > autouse Power::socket { $ENV{WIRED} } Bingo! Ding ding ding!! :-) Something like this could allow a great deal of specification while still not becoming unwieldy. Where should this info be maintained? In a module in @INC (sort of like CPAN/MyConfig.pm)? Or in a special file that's only written to via a module install? Or in a block atop each module that's yanked out via MakeMaker? Or??? -Nate
- 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
- Re: Really auto autoloaded modules Jarkko Hietaniemi
- Re: Really auto autoloaded modules James Mastros
- Re: Really auto autoloaded modules Simon Cozens
- Re: Really auto autoloaded modules Dave Rolsky
- Re: Really auto autoloaded modules Damian Conway
- Re: Really auto autoloaded modules Nathan Wiger
- Re: Really auto autoloaded modules Nathan Wiger
- Re: Really auto autoloaded modules Dan Sugalski
- Re: Really auto autoloaded modules Austin Hastings
- Re: Really auto autoloaded modules Damian Conway
- Re: Really auto autoloaded modules Nathan Wiger
- Re: Really auto autoloaded modules Damian Conway
- RE: Really auto autoloaded modules Dave Storrs
- Re: Really auto autoloaded modules Dan Sugalski
- Re: Really auto autoloaded modules Uri Guttman