Full context and any attached attachments can be found at: <URL: http://rt.cpan.org/NoAuth/Bug.html?id=5708 >When creating a multiple .pl par (i.e. pp -o xyz.par abc.pl def.pl ghi.pl) the various sub .pl programs are not available via:
parl xyz.par abc.pl
due to a bug in the main.pl that is designed for the case where someone has linked to xyz.par as abc.
Hi there, sorry for my belated reply.
This has now been fixed in the snapshot version: http://p4.elixus.org/snap/PAR.tar.gz
If you can test and confirm that it works you, it'd be appreciated. Note that you have to use:
pp -p -o xyz.par def.pl ghi.pl
instead of
pp -o xyz.par def.pl ghi.pl
since the latter builds an executable file, not a PAR file.
Well, actually, that is what I do want to do. I want to build an executable with multiple .pl files in it. I think there is an ambiguity in the specification.
Either you can have multiple .pl in an executable and access them as the first parameter on the command line, *or* you can have support for linking whereby the .exe works out what it was called as and runs the appropriate .pl, but you can't have both at the same time and the first parameter on the command line is the first parameter to the script.
On Windows the former behaviour is preferable since there is no linking to speak of. On Linux, the latter is preferable.
Either way, I think it is going to take another command line option to sort it out :( Either a command line option on pp (to force main.pl not to be included) or on the resulting executable (to override running main.pl). The advantage of the former is that it is easier to use and the advantage of the latter is that you can still use the same executable either way.
I would be happy with either.
I'll be very, very grateful if you can also provide a documentation patch to "pp" that explains this behaviour. :)
I'll happily do this, once we work out what it is that we need to document :)
TIA, Yours, Martin
