Re: Re: removing POD docs from modules

Cool, as an act of pure conceptual art.

However, I wouldn't want to do any work on your system where perldoc Any::Module returns just No documentation found for "Any::Module".

BTW, how many cents worth of storage did you save? Less than one (non-free) beer I bet. Unless you're preparing embedded perl for the next-gen chipcards, in which case I'm utterly impressed!

--
Cheers Joe ;-)

Comment on Re: Re: removing POD docs from modules Download Code

Replies are listed 'Best First'.
Re: Re: Re: removing POD docs from modules by bart (Canon) on Oct 31, 2002 at 20:34 UTC
However, I wouldn't want to do any work on your system where `perldoc Any::Module` returns just No documentation found for "Any::Module". Then put the stripped POD into a .pod file. In other words: put what you extract from Any/Module.pm into a file Any/Module.pod. It works just as dandy with perldoc.	[reply]
Re: Re: Re: Re: removing POD docs from modules by joe++ (Friar) on Nov 01, 2002 at 13:28 UTC
Just wondering if there is any reason to separate POD from Perl source, apart from saving space? My initial reaction whas somewhat ironic, as I didn't see any reason for wanting to do so. But the reply from bart makes me wonder if there is any significant performance penalty at compile time if Perl has to wade through lots of POD sections? I can't hardly imagine that a performance gain from stripping POD is significant, but has this been tested by anyone? Just wondering... -- Cheers, Joe	[reply]