Re: (nrd) removing POD docs from modules

What is there to gain in doing this? The amount of space saved is near insignificant. You will be removing a lot of valuable information: technical documentation, requirements, bug info, and author credit.

If this is really such a hair-splitting issue, why don't you use a text editor to remove the POD from the modules that you see as having excessive documentation?

John J Reiser
newrisedesigns.com

Comment on Re: (nrd) removing POD docs from modules

Replies are listed 'Best First'.
Re: Re: removing POD docs from modules by Kanji (Parson) on Oct 31, 2002 at 18:26 UTC
The amount of space saved is near insignificant. I'm sure there are many modules where the savings would be neglible, but POD makes up 1/2 of CGI.pm and LWP::UserAgent. If that were true for the majority of modules out there, that's a very significant savings, especially if you're playing in enviroments where space is at a premium (embeded systems, flash cards, install CDs). That said, you can save far more space by whittling down a lot of the excess baggage in core distribution than by stripping POD (as touched on in this p5p thread); although doing both should make for a really minimalist Perl install! ;) --k.	[reply]

Replies are listed 'Best First'.

Re: Re: removing POD docs from modules
by Kanji (Parson) on Oct 31, 2002 at 18:26 UTC

The amount of space saved is near insignificant.

I'm sure there are many modules where the savings would be neglible, but POD makes up 1/2 of CGI.pm and LWP::UserAgent. If that were true for the majority of modules out there, that's a very significant savings, especially if you're playing in enviroments where space is at a premium (embeded systems, flash cards, install CDs).

That said, you can save far more space by whittling down a lot of the excess baggage in core distribution than by stripping POD (as touched on in this p5p thread); although doing both should make for a really minimalist Perl install! ;)

--k.

[reply]