Re: C@ un-initialized defer

Its because SwiftX comes up by default in INTERPRETER. INTERPRETER
interactive search order is FORTH then *INTERPRETER so C@ interactively runs
HOST's. INTERPRETER compiling search order is *INTERPRETER then FORTH so C@
compiled runs one vectored (deferred) for use w/ the XTL and TARGET memory).
I meant to be in HOST; that it was left up to the application to define C@
threw me...

SwiftX.pdf 4.5 MEMORY ACCESS
... if you use these words interpretively (e.g., ...in the compile-time part
of
a defining...), they have a special cross-compiler behavior
that depends on whether you are connected to a running target system using
the XTL (see Section 4.9.1).

-----Original Message-----
From: Bulgrien, Dennis
Sent: Tuesday, February 26, 2002 13:36
To: swiftx_at_forth.com
Subject: [swiftx] C@ un-initialized defer

Why can I run C@ interactively before including build.f but get an
"un-initialized defer" error when running a word containing it?

SwiftX 68K 3.1...
: cfetch C@ ; ok
PAD cfetch un-initialized defer

PAD C@ 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!
----------------------------------------------------------------------
THIS LIST IS NOT FOR BUG REPORTS! Send bug reports to support_at_forth.com.
Received on Tue Feb 26 2002 - 12:39:10 PST