Jonathan Lang wrote:
If I understand you correctly, the pain to which you're referring
would come from the possibility of a name that's reserved by the newer
version of Pod, but not by the older version. Wouldn't the simplest
solution be to let a Pod document announce its own version, much like
Perl can?
That would presumably be:
=use 6.0.2
Though it's not quite an exact analogy. If a Perl interpreter isn't recent
enough, it can't really fall back on "best attempt" to execute a program.
Code is either valid or unusable.
For documentation, even if you don't know how to interpret a particular
mark-up, you can always just display it as raw text and the reader can
still get most of the benefit of it.
It's hard to imagine a circumstance in which a refusal to render Pod:
Perldoc v6.0.2 required--this is only v6.0.1, stopped at S26.pod, line 1
would be preferable to actually rendering that Pod, no matter how badly.
Damian
