Ah - I've just discovered that it *will* set Sys$ReturnCode to
zero/nonzero. So with a bit more tweaking, it should be possible to
change MBBack to use that.
However, I did discover that the value of this variable is very
volatile. How safe is it to read? I'm planning on calling wget in a
TaskWindow with Wimp_StartTask, and examining the return code once I get
the TaskCloseDown Wimp message. Is it possible that some other task may
alter its value between wget quitting and MBBack learning of it,
assuming that I am not the only program calling Wimp_Poll in the
desktop?
An alternative solution would be to write a wrapper Obey file and
Wimp_StartTask that, but I'd rather avoid that.
--
__<^>__
/ _ _ \ You always find something in the last place you look.
( ( |_| ) )
\_> <_/ ======================= Martin Bazley ==========================
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
No comments:
Post a Comment