Re: Data storage in paged memory (was DOES>Woes)

> 328000 32BFFF CDATA SECTION PAGE2

<snip>

> I still
> find it confusing what PAGE2 does when IDATA is the current section.
> Page 49 of the SwiftX manual states that "an instance becomes the
> current section when its name is invoked". That says to me that PAGE2
> would invoke CDATA, so PAGE2 CDATA is redundant, consistent with my
> getting the same results with PAGE2 and PAGE2 CDATA.

No, it is absolutely not redundant.

PAGE2 selects the current CDATA instance, but does not force CDATA to be the
current section type. This ia a very important distinction. Having PAGE2
automatically switch you from IDATA to CDATA (at least the way I use
sections) would be a bad side effect! Executing PAGE2 means I'm going to
compile code in that section. But the place I'm putting *data* isn't
changed.

Keep in mind that there are three section types (CDATA, IDATA, and UDATA).
And there may be multiple instances of each type. There are two levels at
work here, and their selection mechanisms operate independently, as they
must!

----------------------------------------------------------------------
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 - 13:06:52 PST