At 11:04 PM 5/23/97 +0000, you wrote:
>>however, it's nice to
>> simply *ignore* bank-switching and related concepts.  If 96 bytes' worth
>> of registers are non-banked, then the vast majority of applications--even
>> those which use up hundreds of bytes worth of arrays--will be able to
>> handle all their non-array needs without bank-switching.
>

BUT, then again...


Lets say you have a set of routines that
>handle some sort of calculations that use an array. Would you put the
>array and the other variables in the same page or not? You don't want to
>limit its use to a single project

IF you are using c language and also dividing up the code into in-line and
realtime parts as in New Micros' (http://www.newmicros.com/isomax.html )
approach, and reusing code, then you would want to make a routine for
starting to execute at a new bank address after one of your real time waits
is done and you have a little in-line code to do to get to the next wait.
in that case, the banks having only a few SFR's related to them is not a
problem since you save the state  of your program every time you get to a
wait state in it. (You save the program state in regular memory somewhere).
If you make a routine or a "word" in your language for going to a new
memory bank, it's not a big deal.

One way to do it is with a virtual machine approach using CFLEA
(http://www.dunfield.com/catalog.html#cflea) by dunfield.

A value added reseller of DDS's CFLEA is
(http://www.sistudio.com/)   although, the fact that they resell and add
onto CFLEA is not on the web site right now..?!...  If interested, give
them a word or two at info@sistudio.com

John Griessen
CIBOLO Metal Works
3406 Hancock Dr Austin TX 78731-5432  512 451-8207
http://www.tpoint.net/~john_g/cibolo/