John Peacock wrote: > Eric Wilhelm wrote: >> Given the absence of a version-pegging include() statement, most of this >> information's usefulness is in the human-readable sector. > > See version::Limit, which does pretty much what Schwern is asking for: > > http://search.cpan.org/dist/version-Limit/ > > It give the module author the ability to make hard limits on compatibility, up > to and including "blacklisting" specific releases or forcing API demarcations. > > The big problem with it is that the consumer of the module must include a > version number on the `use` line for this magic to work. I haven't figured > out > a way to require this (due to the vagaries of Perl's `use` code).
Is this a problem? If the user doesn't specify a version of a module, what would version::Limit do? Or do you want to force the user to require a version? Ick. -- Ahh email, my old friend. Do you know that revenge is a dish that is best served cold? And it is very cold on the Internet!
