> > Is it possible to throw from an external? I haven't done any external
> > development yet although as soon as I see some decent docs I'll
> > probably
> > jump in as I know some C.
>
> I'd be inclined to include a glue stack library with an external. It
> would handle the sugar coating for
On Sunday, July 13, 2003, at 12:13 AM, Monte Goulding wrote:
Is it possible to throw from an external? I haven't done any external
development yet although as soon as I see some decent docs I'll
probably
jump in as I know some C.
I'd be inclined to include a glue stack library with an external.
> > Yes, I was just about to suggest it to Richard. I think this is an under
> > used language feature. Unfortunalty Scott designed the engine throws to
> > require considerable parsing of the error variable to determine
> the problem
> > so you need to handle the possibility of an engine throw. On
Monte Goulding wrote:
>> I readily use throw in scripts for my own use. I also have used it in
>> a library I will make generally available, and I'm thinking of changing
>> the scripts so that they do not throw. Are people comfortable with
>> throw?
>
> Yes, I was just about to suggest it to Ri
> I readily use throw in scripts for my own use. I also have used it in
> a library I will make generally available, and I'm thinking of changing
> the scripts so that they do not throw. Are people comfortable with
> throw?
Yes, I was just about to suggest it to Richard. I think this is an under
On Saturday, July 12, 2003, at 06:11 AM, Richard Gaskin wrote:
Which approach do you prefer? One of these? Something else?
I use these:
1. Reshape the semantics so there are no errors.
2. Throw
3. Value returned in referenced variable and success/fail (or related)
returned.
4. Separate dom
