I recently started deploying my scripts compiled with PAR, and noticed that pod2usage doesn't work with those binaries anymore.
Win32::GUI apps even crash on ms windows.


Sure, after
  pp -o myscript myscript.pl; ./myscript
$0 is a binary and Pod::Usage breaks.

Any thoughts how to circumvent this? Same for compiled srcipts with all other possibilities. (PerlApp/PerlCtrl/PerlSvc/perl2exe/B:C)

PAR could store a magic resource/stream (similar to __DATA__) for POD, and Pod::Parser + Pod::Simple could pick it up from this stream, if $0 is a binary. while (<POD>) { }

See http://jouke.pvoice.org/perl.html for PARcompile and http://jenda.krynicky.cz/perl/ for PDKcompile for some other filters, used to extract build info from POD for those packagers.
But I want to get at the internal POD stream in a general way.


I'm not sure if that trick would be okay for Pod::Perldoc also. There an external .pod file would make more sense. Maybe pod2usage should try to find an external .pod file also on binary scripts, before trying to fetch a magic <POD> stream, which should be provided by p5p.
--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/
http://phpwiki.org/

Reply via email to