Wiggins d Anconia wrote:
It's dangerous to make blanket statements like this. Each is a tool thatI agree with this. Generally system would be the right fit for many of my Perl programs. However exec has it's place like any tool.
should be understood and applied in the right manner.
hmm... So system could generate zombie processes? Or a filehandle process?That is why it is more important to understand the concepts of process execution, parallelism, blocking, etc. rather than any one particular function. 'system' is really just a combination of a fork+exec+waitpid model that is easy to use, the backticks are similar to the open pipe model, but generally easier to use as well, the open pipe model is really just a fancy version of the same fork+exec+waitpid model. So some would claim you should use fork+exec+waitpid, because 'system' really just uses them, others would say that is the beauty of Perl, 'system' provides a very good shortcut, assuming it accomplishes the goal.
I guess it really depends on what we are kicking off and whether it exists cleanly.
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
