David's right. You are looking for the system command.
As to whether tis nobler in the hearts and minds to use Perl pure instead of systeming out to some batch files: Consider this. Your batch files are probably calling executables which, if re-written in perl, your perl program would have to system out to do anyway. Also, if your batch files are working just fine, there is no shame in using perl for process control (which is what we call it if perl is directing the other processes).
I'd probalby convert the batch apps to perl based on how much 'thinking' is done in the batch file. If the batch file is just
Or something simliar, I'd probably just leave it as a batch. But if it's checking for the existence of one file and creating an argument list on the fly based on some flags or something, I might opt to switch to perl. Put bluntly, perl is a LOT smarter than a dos batch file can be.date /t > c:\temp\foo_export.log time /t >> c:\temp\foo_export.log export foo_database > c:\temp\foo_database_export >> c:\temp\foo_expor +t.log date /t >> c:\temp\foo_export.log time /t >> c:\temp\foo_export.log
In reply to Re: Callin batch files from Perl script
by KurtSchwind
in thread Callin batch files from Perl script
by Ethen
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |