Skip Menu |

This queue is for tickets about the PodParser CPAN distribution.

Report information
The Basics
Id: 4894
Status: resolved
Priority: 0/
Queue: PodParser
People
Owner: Nobody in particular
Requestors: michael_scott [...] mac.com
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Sat Jan 10 07:31:54 2004 Guest - Ticket created
Subject: POD::Checker should ignore the contents of strings and HERE documents
Saving the snippet below to a file and running podchecker on it produces the following error twice: *** ERROR: Spurious text after =cut In fact there is no pod in the file. It is in the HERE document and the string. -------SNIP-------- $x = <<HERE; =pod HERE document =cut HERE $y = " =pod string =cut "; print $x; print $y; -------SNIP--------
  Mon Feb 09 06:29:57 2004 Guest - Correspondence added
[guest - Sat Jan 10 07:31:54 2004]: Show quoted text
> Saving the snippet below to a file and running podchecker on it > produces the following error twice: > > *** ERROR: Spurious text after =cut > > In fact there is no pod in the file. It is in the HERE document and > the string.
No pod parser on earth (besides perl) can distinguish pod from a here document/string, and no pod parser attempts to so. I believe the official party line is to not even try.
  Mon Feb 09 06:34:54 2004 Guest - Correspondence added
Heredocs containg pod are better written as ($x = <<'HERE') =~ s/^\t//gm; # no pod here :) =head1 ACTUAL POD yup =cut HERE isn't that marvelous? :)
  Tue May 31 16:07:42 2005 Marek.Rouchal [...] gmx.net - Status changed from 'new' to 'resolved'
  Tue May 31 16:07:42 2005 Marek.Rouchal [...] gmx.net - Correspondence added
You already gave all comments and a very nice solution. Nothing I could add here. Thanks for the input nevertheless, -Marek