If by 'misdirection' you mean "Gee it sure looks like you posted the wrong code..." then you are right on the money. I've updated it with one that does fail, as advertized, the first time through. It should be noted that this program does not actually eval the string on the first line without modifying it heavily. In the case of the old code something like 'print "J.A.P.H \n";%70^72#...' was being eval-ed. As you mention, that line is runnable.
Anyways, I've been trying to figure out how to block error messages and STDOUT generated in functions used in my programs that were written by other people. 'close' seems to work great! Thanks! Do you know how to re-open STDERR and STOUT properly?
In reply to Re^2: J.A.P.H. with intentional eval failure
by ktross
in thread J.A.P.H. with intentional eval failure
by ktross
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |