Re: IOR_FORTHERROR "Throw" error

Mike,

The only place in the code is in the unhandled exception filter
in Exception.f. If windows gets an exception that it doesn't otherwise
know how to handle, it calls the WINCATCH callback, which does a
"IOR_WINEXCEPT THROW" and causes your grief.

Sorry to not be able to help more.

Rick

Friday, October 25, 2002, 12:33:48 PM, you wrote:

MG> Yes, that makes sense.

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

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

MG> -----Original Message-----

MG> Mike,

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

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

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

----------------------------------------------------------------------
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.
Received on Fri Oct 25 2002 - 12:45:26 PDT