comment on

Bravo theorbtwo. From CB discussion to actual preliminary implementation in 24 hours!

One thought on the ability to configure [doc://...] for different POD versions...

You could allow for this type of format: [doc://podname:version]. I know of no POD containing a colon in its name. The trick would be that if the version number is for a version not available on www.perldoc.com, the DWIMery mechanism would go for the next higher or next lower version that does exist on the site. I would vote for "rounding down" to the nearest version. For example, if someone requests the following link: [doc://perlre:5.8.2], which doesn't exist at www.perldoc.com, the mechanism would round down to [doc://perlre:5.8.0].

Also, it may be nice to allow for a user setting that sets the "default" POD version number to be used with the [doc:// tag.

Some of this may be too much work; I don't know what the code looks like.

One other question: Is there a defined behavior if this tag is used on core modules?

Anyway, good job on getting this up and running so fast.

Dave

In reply to Re: New bracket-link stuff by davido
in thread New bracket-link stuff by theorbtwo

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks