moderated >> Crashing perl by pod.

by pkaluski » Sat, 29 Jan 2005 04:32:35 GMT

Hi,
I am under an impression that badly formatted pod in a module can make
perl crash. I didn't find a simple pattern, which would allow to easily
recreate the problem. And in general I find the problem difficult to
recreate.
I am not 100% sure that pod is the culprit here. Therefore I am currious
if anyone had perl crashing due to invalid pod syntax in his/her *.pm files.

--
Piotr Kaluski

"It is the commitment of the individuals to excellence,
their mastery of the tools of their crafts, and their
ability to work together that makes the product, not rules."
("Testing Computer Software" by Cem Kaner, Jack Falk, Hung Quoc Nguyen)


moderated >> Crashing perl by pod.

by Michael Carman » Mon, 31 Jan 2005 00:07:37 GMT



I don't think that POD can make perl crash unless it isn't properly delimited.
In that case perl would try to parse it as code and your module wouldn't
compile. Assuming a module compiles, though, there is no way that I'm aware of
for POD to cause any problems. It should be treated as a comment (and thus be
syntactically inert.)

-mjc

moderated >> Crashing perl by pod.

by Andrei Voropaev » Mon, 31 Jan 2005 16:22:38 GMT


Which version of perl you have? I remember long time ago with one of the
first perl5 versions we had crashes like you describe. If I remember
correctly in our case this was lonely =cut somewhere in the middle of
the module. With latest perl we don't expirience anything like that.


--
Minds, like parachutes, function best when open

moderated >> Crashing perl by pod.

by pkaluski » Wed, 02 Feb 2005 02:21:13 GMT


This is the most recent release taken from www.activestate.com.
OK. It seams that it is not that common to crash perl by pod.
I will come back to this thread once I have a good example.

--
Piotr Kaluski

"It is the commitment of the individuals to excellence,
their mastery of the tools of their crafts, and their
ability to work together that makes the product, not rules."
("Testing Computer Software" by Cem Kaner, Jack Falk, Hung Quoc Nguyen)

Similar Threads

1. Tk::Pod::Search went retro-version in latest release of Tk::Pod

2. POD rendering - was POD: force line break? - Perl

3. solved - POD rendering - was POD: force line break?

On Tuesday 08 August 2006 12:16, Mumia W. wrote:
> On 08/08/2006 04:19 AM, Gary Stainburn wrote:
> > [ snipped ]
> > What's the best way to force the formatting similar to the original
> > layout?
>
> Did you read the perlpod document (perldoc perlpod)?

yes

> Did you read Ken Foskey's response in the thread?

yes

However, I've now re-read ken's response and got it working.  The problem was 
that I was trying combinations of both suggestions and either getting the 
output I posted before, or nothing at all.

I've now removed all the =begin/=end, <pre> etc. from my output and simply
prefixed every line with a space.

I now get the output I wanted.
-- 
Gary Stainburn
 
This email does not contain private or confidential material as it
may be snooped on by interested government parties for unknown
and undisclosed purposes - Regulation of Investigatory Powers Act, 2000     

4. ANNOUNCE: spodcxx v0.21, a (s)POD Parser and (s)POD to HTML converter

5. A (probable) error in perltoot ( perl5/5.8.0/pod/perltoot.pod, line number 756 )

6. ANNOUNCE: spodcxx v0.21, a (s)POD Parser and (s)POD to HTML converter - Perl

7. ANNOUNCE: spodcxx v0.22, a (s)POD Parser and (s)POD to HTML converter

8. VIM: Fold only Perl POD