At 2:23 AM -0500 8/31/02, _brian_d_foy wrote:
>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.
I didn't say I'd make it the *default*--sheesh, perl exceptions are
too darned expensive for that. I said I'd put it in. You still have
to set the
$Mac::AppleScript::yes_I_want_errors_to_be_fatal_no_really_I_do flag
to a true value...
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
