All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

To be fair, when// and//= were last proposed, they were in the form of ||| and |||=. Tom rejected them out-of-hand because they were unperlish, and Larry rejected them because they were too difficult to read and mistype.

Now that Larry's re-blessed the idea as//, things are different, and that's mostly because of a simple respelling of ||| to make it more perlish.

But Tom did drive a lot of people away from working on Pod for a long time. Unfortunately. He did have a point, and that point seems to have lived on: Pod is it's own format, and should be treated as such. Trying to re-invent LaTeX, HTML, XML, DocBook or anything else through Pod isn't going to work; nor is switching Perl's internal documentation format to anything but Pod (or something fundementally Pod-like) ever going to happen -- for good reason.