embedded systems developers tools, cross compilers
  Home  |   SwiftX Archive  |   SwiftForth Archive  |

Re: Identifier Use of _ vs -

From: Howard Lee Harkness <howard.lee.harkness_at_gmail.com>
Date: Thu, 18 Aug 2005 12:45:44 -0500

I would prefer to see some sort of class, struct, or namespace
mechanism that would make this awkwardness unneeded. PolyFORTH had
vocabularies, which worked very nicely for this purpose, but that
feature has been left out of SwiftX. Apparently, Forth, Inc. has
decided that SwiftX is only for small projects where the namespace
does not get unmaintainably large.

On 8/18/05, Bulgrien, Dennis <Dennis.Bulgrien_at_tripointglobal.com> wrote:
<snip>=20
> If I were to create an EQU for a bit in a register there would be several
> choices for the name:
> %00000001 EQU UNITA_REGB_BITC
> %00000001 EQU UNITA-REGB-BITC
> %00000001 EQU UNITA.REGB.BITC
> or given that the register name is already chosen, it would be best to ke=
ep
> that name intact as the prefix...
> %00000001 EQU UNITA_REGB_BITC
> %00000001 EQU UNITA_REGB-BITC
> %00000001 EQU UNITA_REGB.BITC
> %00000001 EQU UNITA_REGB:BITC
> %00000001 EQU UNITA_REGB[BITC]
> etc.
<snip>
--=20
Howard.Lee.Harkness_at_gmail.com
----------------------------------------------------------------------
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 Thu Aug 18 2005 - 10:46:09 PDT

This archive was generated by hypermail 2.2.0 : Tue Dec 02 2008 - 03:04:50 PST