I think this approach definitely has merits. At the company I'm currently working for I've pioneered the use of Perl, so before Perl got "generally accepted" (this took about a year) my colleagues didn't use the software I wrote "because it was too much trouble to install" (not too difficult, mind you, too much trouble: modules and what not).
Life would have been much easier with a tool to bundle software à la PAR or a PRE as suggested in this meditation. At some point a -- gasp -- Visual Basic program was used rather than my Perl code since the latter was a simple executable and the Perl version required installing a few modules.
To conclude: I second this suggestion whole heartedly.
Just my 2 cents, -gjb-
Update: my thanks to grinder for suggesting the correct HTML entity for à.In reply to Re: Should we have PerlC and PRE?
by gjb
in thread Should we have PerlC and PRE?
by dingus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |