On 28 Jul 2004 at 13:19, Glenn Linderman wrote: > > PAR strips POD from all packed modules by default to reduce packaged sizes. > > WinAdj.pm > > must contain some broken POD and PAR is mistakenly stripping out some code. To > > avoid > > this: > > > > set PAR_VERBATIM=1 > > > > before running pp. POD will not be stripped. > > > > Did you modify WinAdj.pm yourself? You might check to see if you broke the POD > > doing > > it. Or try the original WinAdj.pm just to see if it has the POD problem, even if > > it > > isn't the functionality you want. > > I wouldn't know broken POD from a good POD. This POD starts with > > #!/usr/bin/perl > > =header > > bunch of text lines > > =cut > > then script > then later there is > > =usage > > bunch of text lines > > =cut > > then more script. All I really know about POD is that the directives > start with = in column 1. Can you tell me if that is good or bad POD? > Perl knows how to skip it (I guess, it gives no errors on the text > lines), but PAR apparently doesn't know how to strip it.
I probably shouldn't have said "broken", but not "classic". PodStrip.pm is looking specifically for the POD commands listed in the perlpod doc. The commands "=header" and "=usage" are not defined there. I'll look closer at what PodStrip does. Anyway, did "set PAR_VERBATIM=1" work for you? It's there for just this case. Alan Stewart
