hey all,
btw - what's the best way to trace through par to see what its doing ? I'm trying
to trace down issues that I'm having with autoloading, Inline modules, etc.
For example, if you compile some Inline'd code, and then move the executable that
you compiled into a different location, then the executable bails with:
sh: syntax error at line 1: '(' unexpected.
And autoloader doesn't seem to like CODE references very much, I'm getting statements
like:
Can't locate CODE(0x491f44) in @INC (@INC contains: CODE(0x2da354)
CODE(0x491f44) /opt/tools/mdss/test/2.8/lib/perl5/5.8.1/sun4-solaris-64int
/opt/tools/mdss/test/2.8/lib/perl5/5.8.1
/opt/tools/mdss/test/2.8/lib/perl5/site_perl/5.8.1/sun4-solaris-64int
/opt/tools/mdss/test/2.8/lib/perl5/site_perl/5.8.1
/opt/tools/mdss/test/2.8/lib/perl5/site_perl/5.8.0
/opt/tools/mdss/test/2.8/lib/perl5/site_perl .) at
/opt/tools/mdss/test/2.8/lib/perl5/5.8.1/AutoLoader.pm line 156.
which I'm assuming are related errors.
Anyways, any help on this is greatly appreciated.
Ed
(
ps - all-in-all the whole coderef thing seems to be a tenuous fit at best, if
you simply packed perl up, tacked on the modules at the end and untarred them into
a specified location you could probably avoid lots of the headaches, but then
again, I'm sort of hesitant to do that. I'd rather make the present scheme work
for all cases.
)
