Re: EQU vs TARGET : Name conflict

In short, its because the definition of EQU says ['] *TARGET ?CONFLICT .

HOST

: EQU ( x -- )
   ['] *TARGET ?CONFLICT ['] *SHELL ?CONFLICT ['] *COMPILER ?CONFLICT
   CURRENT @ ALSO *EQUATES DEFINITIONS SWAP CONSTANT PREVIOUS CURRENT !
;

I thought it would just redefine it, like the following:
TARGET ok
: x 1 ; ok
: x 2 ;
x isn't unique. ok

Who knows the rationale?

-----Original Message-----
From: swiftx-bounce_at_forth.com [mailto:swiftx-bounce_at_forth.com]On Behalf
Of Bulgrien, Dennis
Sent: Friday, December 03, 2004 9:55
To: 'swiftx_at_forth.com'
Subject: [swiftx] EQU vs TARGET : Name conflict

Why can't there be an EQU with the same name as a target word?

TARGET ok
1 EQU once ok
: once 1.0 ; once Name conflict
----------------------------------------------------------------------
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 - 09:05:05 PST