📄 pl2bat.pl
字号:
eval 'exec perl -x -S "$0" ${1+"$@"}' if 0; # In case running under some shellrequire 5;use Getopt::Std;use Config;$0 =~ s|.*[/\\]||;my $usage = <<EOT;Usage: $0 [-h] or: $0 [-w] [-u] [-a argstring] [-s stripsuffix] [files] or: $0 [-w] [-u] [-n ntargs] [-o otherargs] [-s stripsuffix] [files] -n ntargs arguments to invoke perl with in generated file when run from Windows NT. Defaults to '-x -S "%0" %*'. -o otherargs arguments to invoke perl with in generated file other than when run from Windows NT. Defaults to '-x -S "%0" %1 %2 %3 %4 %5 %6 %7 %8 %9'. -a argstring arguments to invoke perl with in generated file ignoring operating system (for compatibility with previous pl2bat versions). -u update files that may have already been processed by (some version of) pl2bat. -w include "-w" on the /^#!.*perl/ line (unless a /^#!.*perl/ line was already present). -s stripsuffix strip this suffix from file before appending ".bat" Not case-sensitive Can be a regex if it begins with `/' Defaults to "/\.plx?/" -h show this helpEOTmy %OPT = ();warn($usage), exit(0) if !getopts('whun:o:a:s:',\%OPT) or $OPT{'h'};$OPT{'n'} = '-x -S "%0" %*' unless exists $OPT{'n'};$OPT{'o'} = '-x -S "%0" %1 %2 %3 %4 %5 %6 %7 %8 %9' unless exists $OPT{'o'};$OPT{'s'} = '/\\.plx?/' unless exists $OPT{'s'};$OPT{'s'} = ($OPT{'s'} =~ m#^/([^/]*[^/\$]|)\$?/?$# ? $1 : "\Q$OPT{'s'}\E");my $head;if( defined( $OPT{'a'} ) ) { $head = <<EOT; \@rem = '--*-Perl-*-- \@echo off perl $OPT{'a'} goto endofperl \@rem ';EOT} else { $head = <<EOT; \@rem = '--*-Perl-*-- \@echo off if "%OS%" == "Windows_NT" goto WinNT perl $OPT{'o'} goto endofperl :WinNT perl $OPT{'n'} if NOT "%COMSPEC%" == "%SystemRoot%\\system32\\cmd.exe" goto endofperl if %errorlevel% == 9009 echo You do not have Perl in your PATH. if errorlevel 1 goto script_failed_so_exit_with_non_zero_val 2>nul goto endofperl \@rem ';EOT}$head =~ s/^\t//gm;my $headlines = 2 + ($head =~ tr/\n/\n/);my $tail = "\n__END__\n:endofperl\n";@ARGV = ('-') unless @ARGV;foreach ( @ARGV ) { process($_);}sub process { my( $file )= @_; my $myhead = $head; my $linedone = 0; my $taildone = 0; my $linenum = 0; my $skiplines = 0; my $line; my $start= $Config{startperl}; $start= "#!perl" unless $start =~ /^#!.*perl/; open( FILE, $file ) or die "$0: Can't open $file: $!"; @file = <FILE>; foreach $line ( @file ) { $linenum++; if ( $line =~ /^:endofperl\b/ ) { if( ! exists $OPT{'u'} ) { warn "$0: $file has already been converted to a batch file!\n"; return; } $taildone++; } if ( not $linedone and $line =~ /^#!.*perl/ ) { if( exists $OPT{'u'} ) { $skiplines = $linenum - 1; $line .= "#line ".(1+$headlines)."\n"; } else { $line .= "#line ".($linenum+$headlines)."\n"; } $linedone++; } if ( $line =~ /^#\s*line\b/ and $linenum == 2 + $skiplines ) { $line = ""; } } close( FILE ); $file =~ s/$OPT{'s'}$//oi; $file .= '.bat' unless $file =~ /\.bat$/i or $file =~ /^-$/; open( FILE, ">$file" ) or die "Can't open $file: $!"; print FILE $myhead; print FILE $start, ( $OPT{'w'} ? " -w" : "" ), "\n#line ", ($headlines+1), "\n" unless $linedone; print FILE @file[$skiplines..$#file]; print FILE $tail unless $taildone; close( FILE );}__END__=head1 NAMEpl2bat - wrap perl code into a batch file=head1 SYNOPSISB<pl2bat> B<-h>B<pl2bat> [B<-w>] S<[B<-a> I<argstring>]> S<[B<-s> I<stripsuffix>]> [files]B<pl2bat> [B<-w>] S<[B<-n> I<ntargs>]> S<[B<-o> I<otherargs>]> S<[B<-s> I<stripsuffix>]> [files]=head1 DESCRIPTIONThis utility converts a perl script into a batch file that can beexecuted on DOS-like operating systems. This is intended to allowyou to use a Perl script like regular programs and batch files whereyou just enter the name of the script [probably minus the extension]plus any command-line arguments and the script is found in your B<PATH>and run.=head2 ADVANTAGESThere are several alternatives to this method of running a Perl script. They each have disadvantages that help you understand the motivationfor using B<pl2bat>.=over=item 1 C:> perl x:/path/to/script.pl [args]=item 2 C:> perl -S script.pl [args]=item 3 C:> perl -S script [args]=item 4 C:> ftype Perl=perl.exe "%1" %* C:> assoc .pl=Perl then C:> script.pl [args]=item 5 C:> ftype Perl=perl.exe "%1" %* C:> assoc .pl=Perl C:> set PathExt=%PathExt%;.PL then C:> script [args]=backB<1> and B<2> are the most basic invocation methods that should work onany system [DOS-like or not]. They require extra typing and requirethat the script user know that the script is written in Perl. Thisis a pain when you have lots of scripts, some written in Perl and somenot. It can be quite difficult to keep track of which scripts need tobe run through Perl and which do not. Even worse, scripts often getrewritten from simple batch files into more powerful Perl scripts inwhich case these methods would require all existing users of the scriptsbe updated.B<3> works on modern Win32 versions of Perl. It allows the user toomit the ".pl" or ".bat" file extension, which is a minor improvement.B<4> and B<5> work on some Win32 operating systems with some commandshells. One major disadvantage with both is that you can't use themin pipelines nor with file redirection. For example, none of thefollowing will work properly if you used method B<4> or B<5>: C:> script.pl <infile C:> script.pl >outfile C:> echo y | script.pl C:> script.pl | moreThis is due to a Win32 bug which Perl has no control over. This bugis the major motivation for B<pl2bat> [which was originally writtenfor DOS] being used on Win32 systems.Note also that B<5> works on a smaller range of combinations of Win32systems and command shells while B<4> requires that the user knowthat the script is a Perl script [because the ".pl" extension mustbe entered]. This makes it hard to standardize on either of thesemethods.=head2 DISADVANTAGESThere are several potential traps you should be aware of when youuse B<pl2bat>.The generated batch file is initially processed as a batch file eachtime it is run. This means that, to use it from within another batchfile you should preceed it with C<call> or else the calling batchfile will not run any commands after the script: call script [args]Except under Windows NT, if you specify more than 9 arguments tothe generated batch file then the 10th and subsequent argumentsare silently ignored.Except when using F<CMD.EXE> under Windows NT, if F<perl.exe> is notin your B<PATH>, then trying to run the script will give you a generic"Command not found"-type of error message that will probably make youthink that the script itself is not in your B<PATH>. When usingF<CMD.EXE> under Windows NT, the generic error message is followed by"You do not have Perl in your PATH", to make this clearer.On most DOS-like operating systems, the only way to exit a batch fileis to "fall off the end" of the file. B<pl2bat> implements this bydoing C<goto :endofperl> and adding C<__END__> and C<:endofperl> asthe last two lines of the generated batch file. This means:=over=item No line of your script should start with a colon.In particular, for this version of B<pl2bat>, C<:endofperl>,C<:WinNT>, and C<:script_failed_so_exit_with_non_zero_val> should notbe used.=item Care must be taken when using C<__END__> and the C<DATA> file handle.One approach is: . #!perl . while( <DATA> ) { . last if /^__END__$/; . [...] . } . __END__ . lines of data . to be processed . __END__ . :endofperlThe dots in the first column are only there to prevent F<cmd.exe> to interpretthe C<:endofperl> line in this documentation. Otherwise F<pl2bat.bat> itselfwouldn't work. See the previous item. :-)=item The batch file always "succeeds"The following commands illustrate the problem: C:> echo exit(99); >fail.pl C:> pl2bat fail.pl C:> perl -e "print system('perl fail.pl')" 99 C:> perl -e "print system('fail.bat')" 0So F<fail.bat> always reports that it completed successfully. Actually,under Windows NT, we have: C:> perl -e "print system('fail.bat')" 1So, for Windows NT, F<fail.bat> fails when the Perl script fails, butthe return code is always C<1>, not the return code from the Perl script.=back=head2 FUNCTIONBy default, the ".pl" suffix will be stripped before adding a ".bat" suffixto the supplied file names. This can be controlled with the C<-s> option.The default behavior is to have the batch file compare the C<OS>environment variable against C<"Windows_NT">. If they match, ituses the C<%*> construct to refer to all the command line argumentsthat were given to it, so you'll need to make sure that works on yourvariant of the command shell. It is known to work in the F<CMD.EXE> shellunder Windows NT. 4DOS/NT users will want to put a C<ParameterChar = *>line in their initialization file, or execute C<setdos /p*> inthe shell startup file.On Windows95 and other platforms a nine-argument limit is imposedon command-line arguments given to the generated batch file, sincethey may not support C<%*> in batch files.These can be overridden using the C<-n> and C<-o> options or thedeprecated C<-a> option.=head1 OPTIONS=over 8=item B<-n> I<ntargs>Arguments to invoke perl with in generated batch file when run fromWindows NT (or Windows 98, probably). Defaults to S<'-x -S "%0" %*'>.=item B<-o> I<otherargs>Arguments to invoke perl with in generated batch file except whenrun from Windows NT (ie. when run from DOS, Windows 3.1, or Windows 95).Defaults to S<'-x -S "%0" %1 %2 %3 %4 %5 %6 %7 %8 %9'>.=item B<-a> I<argstring>Arguments to invoke perl with in generated batch file. SpecifyingB<-a> prevents the batch file from checking the C<OS> environmentvariable to determine which operating system it is being run from.=item B<-s> I<stripsuffix>Strip a suffix string from file name before appending a ".bat"suffix. The suffix is not case-sensitive. It can be a regex ifit begins with `/' (the trailing '/' is optional and a trailingC<$> is always assumed). Defaults to C</.plx?/>.=item B<-w>If no line matching C</^#!.*perl/> is found in the script, then sucha line is inserted just after the new preamble. The exact linedepends on C<$Config{startperl}> [see L<Config>]. With the B<-w>option, C<" -w"> is added after the value of C<$Config{startperl}>.If a line matching C</^#!.*perl/> already exists in the script,then it is not changed and the B<-w> option is ignored.=item B<-u>If the script appears to have already been processed by B<pl2bat>,then the script is skipped and not processed unless B<-u> wasspecified. If B<-u> is specified, the existing preamble is replaced.=item B<-h>Show command line usage.=back=head1 EXAMPLES C:\> pl2bat foo.pl bar.PM [..creates foo.bat, bar.PM.bat..] C:\> pl2bat -s "/\.pl|\.pm/" foo.pl bar.PM [..creates foo.bat, bar.bat..] C:\> pl2bat < somefile > another.bat C:\> pl2bat > another.bat print scalar reverse "rekcah lrep rehtona tsuj\n"; ^Z [..another.bat is now a certified japh application..] C:\> ren *.bat *.pl C:\> pl2bat -u *.pl [..updates the wrapping of some previously wrapped scripts..] C:\> pl2bat -u -s .bat *.bat [..same as previous example except more dangerous..]=head1 BUGSC<$0> will contain the full name, including the ".bat" suffixwhen the generated batch file runs. If you don't like this,see runperl.bat for an alternative way to invoke perl scripts.Default behavior is to invoke Perl with the B<-S> flag, so Perl willsearch the B<PATH> to find the script. This may have undesirableeffects.On really old versions of Win32 Perl, you can't run the scriptvia C:> script.bat [args]and must use C:> script [args]A loop should be used to build up the argument list when not onWindows NT so more than 9 arguments can be processed.See also L</Disadvantages>.=head1 SEE ALSOperl, perlwin32, runperl.bat=cut
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -