Re: TARGET : <name> ORDER

Ok, well then it maybe this is over my head...

I used the following logic - which is certainly not based on an
intimate knowledge of FORTH. An EQU might not be a "name", but
rather an identifier that is an address to a location where the
value is stored. Since it is visible in TARGET, it would have be
referenceable on the target in target space - but I guess if EQU
is only used during interpreting/compiling, this might be a wrong
thought. I sort of figured an EQU might let you reference a
value one place (at run-time) so you would not have to have
multiple copies of the same constant hanging around. If this
were the case, it seemed like you could not have a "word" with the
same name as an identifier that signifies and address. Maybe this
makes no sense at all? Perhaps it has to do with my not knowing
how interpreting/compiling/runtime works.

But now I see Elizabeth implied that the manual was incorrect with
respect to EQU, but did not directly come out and say that it was.
So, does Forth Inc. know that the .pdf must change based on her
answer? It doesn't appear that they acknowledged that it does.

> -----Original Message-----
> From: swiftx-bounce_at_forth.com
> [mailto:swiftx-bounce_at_forth.com] On Behalf Of Bulgrien, Dennis
> Sent: Friday, December 03, 2004 10:22 AM
> To: 'swiftx_at_forth.com'
> Subject: [swiftx] Re: TARGET : <name> ORDER
>
>
> What I'm trying to figure out is why his help sheet said that
> when compiling a TARGET definition a word is searched for in
> *COMPILER first, if not found *TARGET is searched, if not
> found *SHELL. I wonder if *EQUATES should be in there somewhere.
>
> -----Original Message-----
> Sent: Friday, December 03, 2004 9:21
>
> Mike Erdmann once [created] a vocabulary search order help sheet...
> ----------------------------------------------------------------------
> swiftx_at_forth.com The SwiftX programming discussion email list
> To unsubscribe, send subject "unsubscribe" to
> swiftx-request_at_forth.com For list command help, send subject
> "help" to swiftx-request_at_forth.com Message archives are
> located at http://www.forth.com/archive/swiftx
> ----------------------------------------------------------------------
> This list is a forum for SwiftX users. For product support and bug
> reports, please send email to support_at_forth.com
> ----------------------------------------------------------------------
>
>
> CONFIDENTIAL/PROPRIETARY
>
> Unless otherwise indicated, all information (including
> attachments) contained in this e-mail communication is
> confidential and proprietary information exclusively owned by
> the sender and/or its related or affiliated companies and
> shall not, without the prior written consent of the sender,
> be used, disclosed, distributed or reproduced, in whole or in
> part, by anyone other than the individual or entity to whom
> this communication is addressed exclusively for the purpose
> expressly indicated in this communication.
>
> This e-mail communication is intended for the use of the
> individual or entity to whom it is addressed. If you are not
> the intended recipient of this communication, you are hereby
> notified that any use, dissemination, distribution or copying
> of this communication is strictly prohibited. If you have
> received this communication in error, please destroy any
> copies, electronic, paper or otherwise that you may have.
>
----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
For list command help, send subject "help" to swiftx-request_at_forth.com
Message archives are located at http://www.forth.com/archive/swiftx
----------------------------------------------------------------------
This list is a forum for SwiftX users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Fri Dec 03 2004 - 08:53:36 PST