Re^3: executing a shell script from perl

Point taken JavaFan - can't disagree with any of that - I was obviously in too much of a hurry to give it [my response] anything like a _decent_ coating of thinking about ... in which case I'd've done something similar.

Having said that, since system returns nothing except a return code c/w a signal number, > /dev/null is self-evidently superfluous.

Update:

In the light of the update from brother JavaFan, I refer the reader to my last response - which is self-prophesying since I self-evidently give that no thought either - my comment was true from the POV of view of returning output back to the script, but manifestly wrong from the user POV.

A user level that continues to overstate my experience :-))

Comment on Re^3: executing a shell script from perl Select or Download Code

Replies are listed 'Best First'.
Re^4: executing a shell script from perl by JavaFan (Canon) on Jan 13, 2009 at 16:49 UTC
Having said that, since system returns nothing except a return code c/w a signal number, > /dev/null is self-evidently superfluous. Not at all. There's a big difference between: `system "ls -l /etc > /dev/null";` [download] and `system "ls -l /etc"` [download] The former will not print anything. The latter will print the content of `/etc`.	[reply] [d/l] [select]