Subj : Re: Error handling
To   : Braden McDaniel <bmcdaniel@objectsciences.com>
From : Brendan Eich <brendan@meer.net>
Date : Tue Aug 05 2003 03:29 pm

Braden McDaniel wrote:

>>I didn't have time to look further last night, but now it seems to me
>>that we need another callback, at least, akin to JSErrorCallback but
>>with a JSExnType result.  Or, we could jam a JSExnType member into
>>JSErrorFormatString and copy that result-member into a new
>>JSReport.exnType member.  Either approach requires embedding code
>>changes; the latter avoids yet another callback.  Comments?
>>    
>>
>
>The latter is a bit ugly, at least in that adding an exception type member
>would make JSErrorFormatString seem misnamed. I'm not sure it's wise to
>change the semantics of What that struct Is. Yet Another Callback doesn't
>strike me as particularly onerous given the existing design.
>

Agreed.  Yet another callback coming up.

/be

.