Re: IOR_FORTHERROR "Throw" error

From: Mike Ghan <mikeghan_at_logix-controls.com>
Date: Fri, 25 Oct 2002 12:33:48 -0700

Yes, that makes sense.

But what would cause a IOR_FORTHERROR error? Common exception errors
are handled explicitly (e.g. 0 @ Access Violation, 0 / Divide by
Zero etc). You have probably guessed I've got a IOR_FORTHERROR bug -
my brain is smokin' too.

Mike

PS - I can wait if your brain needs to cool.

-----Original Message-----
From: sftalk-bounce_at_forth.com [mailto:sftalk-bounce_at_forth.com]On
Behalf
Of Rick VanNorman
Sent: Friday, October 25, 2002 12:16 PM
To: Mike Ghan
Subject: [sftalk] Re: IOR_FORTHERROR "Throw" error

Mike,

When a windows error had happens, the global error frame catches
the error, and causes SwiftForth to execute a "normal" THROW with
IOR_WINEXCEPT on the stack. IOR_WINEXCEPT is detected by THROW, which
emplaces IOR_FORTHERROR into the windows trap handler and continues
from there.

The reason is to force THROW to snapshot the registers, return and
data stack. These are available to .EXCEPT .

My brain is smoking now, so even though this is not a complete answer,
I'll quit now.

Rick

Friday, October 25, 2002, 12:01:03 PM, you wrote:

MG> What type(s) of bugs cause a "Throw" IOR_FORTHERROR exception (not
to
MG> be confused with CATCH THROW).

MG> Refer to Exception.F and Except.F (yikes)

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe sftalk" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/sftalk -- check them out!
Search the archives! Visit http://www.forth.com/search for details.

This archive was generated by hypermail 2.2.0 : Fri Nov 21 2008 - 03:04:25 PST