comment on

note that backticks will have to wait for the program to finish and all buffers to be flushed before giving the output, while exec() will just switch to the new program and should be inherently faster than backticks; backticks uses pipes / fork / exec (oh yes, and the shell, as jwkrahn said) to accomplish its magic.

Also note that the two programs aren't at all equivalent, since a successful call to exec() never returns. (You probably know that, but still).

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to Re: exec vs. backtick-and-assign performance by Joost
in thread exec vs. backtick-and-assign performance by apotheon

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