Re: suggestion for an unambiguous hex notation
- From: George Hubert <georgeahubert@xxxxxxxxxxx>
- Date: 28 Apr 2007 04:55:26 -0700
On 28 Apr, 02:13, Frank Buss <f...@xxxxxxxxxxxxx> wrote:
Is this ANS Forth compatible? Looks like most people in this newsgroup are
thinking that writing to "base" is possible, but I'm not sure about the
"postpone". Win32Forth says "Warning(-4101): LITERAL is a system word in an
application word", but looks like it works. What does the warning mean and
is it possible, that it doesn't work in other ANS Forth implementations?
Win32Forth allows programmers to specify whether threaded code (but
not
assembler) and data are placed in normal application space or in
system
space (which includes the name space). Since system space is discarded
from TURNKEYed applications then the systems warns you that your word
cannot be used in such an application. Since it's only use is at
compile
time (like LITERAL) then that shouldn't be a problem. If don't want
the
warning then (since your code won't be used in applications) you can
use;
in-system
......your code....
in-application
to avoid the warning.
George Hubert
--
Frank Buss, f...@xxxxxxxxxxxxxxxxx://www.frank-buss.de,http://www.it4-systems.de
.
- References:
- suggestion for an unambiguous hex notation
- From: Frank Buss
- suggestion for an unambiguous hex notation
- Prev by Date: Re: Forth and Co - The Return of the Jedi
- Next by Date: Re: Forth and Co - The Return of the Jedi
- Previous by thread: Re: suggestion for an unambiguous hex notation
- Next by thread: Re: suggestion for an unambiguous hex notation
- Index(es):
Relevant Pages
|