On 27 Jul 2004 at 21:37, Glenn Linderman wrote: > One module, named WinAdj.pm, was included, but preprocessed (not sure > why it needed to be preprocessed, or what the point of the preprocessing > was). The preprocessed version has a number of #line directives added; > it has ^M added (the original had only ^J for line endings), and had > both =cut directives removed from its pod. One of them (fortunately) > resulted in the load-time "return 1;" statement being logically omitted, > which caused an immediate error when running app.exe. > > I'm neither a POD nor PAR expert (this module was derived from someone > else's which is why it contains POD at all [insert sheepish grin here]), > but when I diffed the files and added the =cut lines back in in the copy > in the not-cleaned PAR temp directory, then I got past this error. > > Can anyone point me in the right direction to understand and/or fix this > behavior? I can't be telling people to fix their PAR temp directory > contents after the first failed run :) I'd be happy to provide the > module source for this module, if it helps. > >
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. Alan Stewart
