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

Re: Sections and section types (was Re: Data storage in paged memory (was DOES>Woes))

From: Ron Oliver <roliver_at_openesque.com>
Date: Sat, 10 Jan 2004 23:44:39 -0500 (EST)

On Sat, 10 Jan 2004, Ron Oliver wrote:

 Each section keeps track of its own "HERE", so you don't have to.
> In chipFORTH, by contrast, if you wanted to have a font table
> somewhere in ROM, you'd have to have something to keep track of how
> much of the table is used up, and you couldn't use , (comma), ALLOT,
> etc. Here, you can.

Well, actually, that's not quite true. Apologies...it's been a long
time since I've used chipFORTH.

In chipFORTH, you could ORG to a new location in ROM, then GAP or
,(comma) from there. Then you'd have to ORG back to the previous
HERE. I don't recall a "nice" way to re-ORG RAM. With properly
defined SwiftX sections, you don't even have to do that, as each
section has its own HERE pointer.

-- 
Ron Oliver <roliver_at_openesque.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 Sat Jan 10 2004 - 20:46:49 PST

This archive was generated by hypermail 2.2.0 : Mon Dec 01 2008 - 03:04:48 PST