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).
But it is possible and may be a way to start the discussion about how to do this
in META.yml instead...
John
