In article <a05111b01b99613226fd2@[63.120.19.221]>, Dan Sugalski <[EMAIL PROTECTED]> wrote:
> >The difference is primarily in the cases when a programmer *forgets* > >to handle an error. Uncaught exceptions force you to take notice, > >whereas uncaught error values don't do much of anything. They just > >let some other problem happen later. > Oh, alright, you've convinced me. I'll put it in the next rev. > (Though I reserve the right to be cranky about it) this will make me use several lines of code everywhere i just have one for RunAppleScript. i'll have to do extra error checking in the middle-ware because the lowe level code decided to do make flow decisions. if other people want their code to die when things don't work, that's fine, but don't make me do that. it's a very useful module, but i won't use it if you make the change, personally, unless you give a way to turn it completely off (although i'd rather you provide a way to turn it on instead :).
