On Wed, 2003-08-06 at 12:01, [EMAIL PROTECTED] wrote:
> That is not true. It merely strips POD sections.
>
> > I tried to pack some app that uses Net::LDAP::Constant which reads and
> > parses its own POD located after __DATA__.
I stand corrected: stuff in __DATA__ gets packed in _except_ POD st
On Wed, Aug 06, 2003 at 12:26:35PM +0200, Roderich Schupp wrote:
> One heuristic might be to turn off POD stripping beyond __DATA__ :)
Very reasonable. The snapshot build (http://p4.elixus.org/snap/PAR.tar.gz)
now preserves everything after __DATA__ -- maybe you can test it a bit?
> Another migh
On Wed, 2003-08-06 at 15:14, [EMAIL PROTECTED] wrote:
> On Wed, Aug 06, 2003 at 12:26:35PM +0200, Roderich Schupp wrote:
> > One heuristic might be to turn off POD stripping beyond __DATA__ :)
>
> Very reasonable. The snapshot build (http://p4.elixus.org/snap/PAR.tar.gz)
> now preserves everythin
On Wed, Aug 06, 2003 at 10:53:27AM +0200, Roderich Schupp wrote:
> apparently pp strips everything beyond __DATA__ from the files
> it packs (as of PAR 0.72).
That is not true. It merely strips POD sections.
> I tried to pack some app that uses Net::LDAP::Constant which reads and
> parses its ow
Hi,
apparently pp strips everything beyond __DATA__ from the files
it packs (as of PAR 0.72). PAR::Intro briefly mentions a solution
for this problem, but continues "no longer needed in recent versions".
In case someone wonders, I tried to pack some app that uses
Net::LDAP::Constant which reads and
