Re: TARGET fixes DISCONNECT

Some may have thought that I accidentally deleted the line between 17 and
18; I did not. That was left out by SwiftX because of an ABORT caused by
trying to execute a word when disconnected. I'll try to simplify it. The
issue that confused me was that TARGET changes Context differently according
to connected status. See how line 7 aborts and line 9 executes... TARGET
"fixes" DISCONNECT by removing *TARGET from Context.

CONNECT TARGET ORDER
 Context: *TARGET *EQUATES *INTERPRETER
 Current: *TARGET ok
.S
<-Top ok
DISCONNECT ok
.S
TARGET ok
.S
<-Top ok
ORDER
 Context: *EQUATES *INTERPRETER
 Current: *TARGET ok
----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe swiftx" 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/swiftx -- check them out!
Received on Thu Jan 03 2002 - 08:34:36 PST