WOW…
if a [:resolve abc.com] doesn’t resolve to something, this appears to fatally crash the script.
[There were reports of this back several years ago, but it still seems to be the case on 5.12]
Is this still everyone else’s experience also?
Is there a reasonable work-around?
The only work around I have seen is to have the resolve happen in a “sub script” using the undocumented :execute command - and passing the parameters back and forth via global vars.
(and using global vars sucks, because if you have multiple scripts doing resolutions, you can’t be sure what’s going to happen - unless you use unique globals for each resolve calling script and each “resolver” script.)
I really like 90% or ROS, but the error handling in ROS is simply HORRID. Scripting is pretty good for rudimentary tasks, but start doing anything very complicated and it really lacks features - or the work-arounds are just really lame.
-Greg