Mark Schonewille wrote:
Hi Chipp,
Weird. I would expect all pros to know about it.
I'd say, give it a try. execute the following script
on foo
try
executeNonExistingHandler
catch myErr
put myErr
end try
end foo
I doubt many pros would need a lookup to figure out that a non-existent
handler would result in a "can't find handler" error. ;)
But seriously, most devs using try/catch setups won't be executing
random code, they'll be working on things that are somewhat well
defined, and use their own error messages to report to the user. I
don't know of any dev who report RunRev's messages to their users; they
just don't provide enough guidance for the user.
Those so inclined can just use the same list everything else in the
LiveCode world uses, the one RunRev provides for us in their
revErrorDisplay stack:
get line (item 1 of tErr) of the cErrorsList of cd 1 \
of stack "revErrorDisplay" into tList
Section 10.4 ("Custom Error handling") of the LiveCode User Guide covers
this well.
--
Richard Gaskin
Fourth World
LiveCode training and consulting: http://www.fourthworld.com
Webzine for LiveCode developers: http://www.LiveCodeJournal.com
LiveCode Journal blog: http://LiveCodejournal.com/blog.irv
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
