The more important problem is that the variables are all mapped into a
contiguous workspace that is referenced so continously that it's
highly unlikely it
would ever get paged from memory, while your process is running, except
perhaps on systems that were so woefully underbuilt that paging
BASIC variables
would be the least of your problems.
The distinction with using an EOF variable is that it is not referenced,
until the next READNEXT. Each new variable that is read into memory will
push the EOF variable further to the back. This definitely caused frame
faults (I think that's what they were called) on Advanced Pick. On either
U2 systems or on properly built systems, I doubt it makes a bit of
difference, it might even slow things down.
Charlie Rubeor
I challenge whatever book made this contention. In the original Pick
architecture variable descriptors are 10 bytes each and live together
in groups of 50 or more (as was alluded to above). Since the EOF is a
single character it would fit in the descriptor itself. In order for
the EOF variable to be "swapped out" of memory for lack of reference,
all other variables whose descriptors live in the same frame as the
EOF variable would have to be unreferenced for the same period of
time -- highly unlikely.
Stewart
--
Stewart Leicester | http://www.ThreatFocus.com
V.P. Engineering | mailto:[EMAIL PROTECTED]
Threat Focus, Inc. | 925-551-0130 Voice
"Knowledge is your best defense" | 509-695-1373 Fax
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
