> > ok then I think system is more ideal for most situations. > It's dangerous to make blanket statements like this. Each is a tool that should be understood and applied in the right manner. 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.
Bottom line is that it is really the situation that will dictate which is "best". And "more ideal for most situations" really becomes a function of the type of job you are in, the type of code you usually find yourself working on, and what you consider to be "production" level of quality. Just a couple of cents, http://danconia.org -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
