It is useful to remember that qx// is backticks. It's just another syntax to get there. It doesn't exercise any different code path, it won't behave any different, except how the parser finds the end of the string (you could type qx/foo `blah`/ without needing special escape characters to get the backquotes into the shell).
Also, q// is single-quoted, and qq// is double-quoted. Same thing.
-- [ e d @ h a l l e y . c c ]
| [reply] [Watch: Dir/Any] [d/l] [select] |
Thank you for your replies.
I attempted the solution using qx but I had the same result. Executing the command using the shell seems to be the problem, the sigalrm is not delivered. It's an interesting problem I haven't come across before.
I was considering using system to redirect the output of the command to a temporary text file and then reading the tmp file to parse output one line at a time.
I should also mention I am working on Win32 Boo! ;)
Nemo | [reply] [Watch: Dir/Any] |
qx and `` produce the same code.
| [reply] [Watch: Dir/Any] [d/l] [select] |