comment on

By growing level of sophistication:

The first set: these calls either replace the current process (exec) or spawn a child process and wait for it (system). The called program can be any executable, they're not limited to Perl. In fact, they're wrappers for the system calls fork and exec, with some added glue.

The second set: these calls are used to import Perl code contained in an external file into the running Perl process.

Take a look at the docs to see what which one does and how the more sophisticated calls can be explained in terms of the lesser ones. Any one of them can be useful in a given situation (sometimes use is not what you want!).

There are more options, especially if you want to communicate with the child process by STDIN/STDOUT/STDERR: open (see also perlopentut), qx// and backticks (in perlop) and the IPC family of modules (IPC::Open2 and IPC::Open3 are useful) etc.

In reply to Re: execute a perl program by calin
in thread execute a perl program by myraleen

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks