Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fix some bad POD links

  • Loading branch information...
commit d3df9108597d6d3896980228b417fec9dc92c7f7 1 parent a554d11
Dave Rolsky authored
2  lib/DateTime/Format/Builder.pm
@@ -679,7 +679,7 @@ present. I lied. There are actually three of them.
679 679
680 680 B<parsers> takes a hashref of methods and their parser
681 681 specifications. See the
682   -L<tutorial above|/"CREATING A CLASS"> for details.
  682 +L<DateTime::Format::Builder::Tutorial> for details.
683 683
684 684 Note that if you define a subroutine of the same name as one
685 685 of the methods you define here, an error will be thrown.
4 lib/DateTime/Format/Builder/Parser.pm
@@ -114,7 +114,7 @@ my @callbacks = qw( on_match on_fail postprocess preprocess );
114 114
115 115 These parameters appear for all parser implementations.
116 116 These are primarily documented in
117   -L<the main docs|DateTime::Format::Builder/"SINGLE SPECIFICATIONS">.
  117 +L<DateTime::Format::Builder>.
118 118
119 119 =over 4
120 120
@@ -261,7 +261,7 @@ returned (it is assumed to be appropriate).
261 261
262 262 The single specification (if not a coderef) can be either a
263 263 hashref or a hash. The keys and values must be as per the
264   -L<specification|/"SINGLE SPECIFICATIONS">.
  264 +specification.
265 265
266 266 It is here that any arrays of callbacks are unified. It is
267 267 also here that any parser implementations are used. With

0 comments on commit d3df910

Please sign in to comment.
Something went wrong with that request. Please try again.