No, it is documented not to load, because its junk
perl doesn't care how pod is started, only how it ends
$ perldoc junk No documentation found for "junk". $ cat junk =cut =cut =cut print "what? \n"; __END__ $ perldoc junk No documentation found for "junk". $ perl junk $ perl -MO=Deparse junk junk syntax OK $ perl -MPod::Simple::Checker -e "exit Pod::Simple::Checker->filter(s +hift)->any_errata_seen" junk junk -- POD ERRORS Hey! The above document had some coding errors, which are explained be +low: Around line 1: =cut found outside a pod block. Skipping to next block. Around line 3: =cut found outside a pod block. Skipping to next block. Around line 5: =cut found outside a pod block. Skipping to next block.
In reply to Re: Excess =cut breaks module
by Anonymous Monk
in thread Excess =cut breaks module
by denishowe
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |