Re: A89: Re: Archive memory

To: assembly-89@lists.ticalc.org
Subject: Re: A89: Re: Archive memory
From: Niklas Brunlid <e96nbr@efd.lth.se>
Date: Wed, 28 Jul 1999 15:04:12 +0200
Delivered-To: assembly-89-outgoing@towerguard.unix.edu.sollentuna.se
Delivered-To: assembly-89@lists.ticalc.org
In-Reply-To: <379EBF23.A18C563@gte.net>
References: <LOBBIDAKFNHMLPNHPGLOGEDBCAAA.filipepinto@mail.telepac.pt> <008b01bed86c$8aa92100$4d0b0923@brabeler>
Reply-To: assembly-89@lists.ticalc.org

At 10:28 1999-07-28 , you wrote:

>By the way, why can't libraries be placed in archive memory?  Libraries don't
>need to be written to do they?

Some libraries (speaking for my own ones here) use variables and/or buffers 
but that can be fixed by using BSS variables instead - unless something 
needs to be saved for the next time it's run...

An idea would be to have a flag in DoorsOS (or whatever) programs that 
tells the system that the program/library will modify itself in some way 
when it's running. If the flag is set - copy it to memory and run it from 
there, then possibly copy it back (could be another flag). If the flag 
isn't set - run it straight from the archive memory. IIRC it's just as fast 
but you'll need less free real RAM.

  / Niklas Brunlid
Check out Prosit for the TI-89 / TI-92 Plus at http://c625.sparta.lu.se
Random PQF Quote follows:

"Seems I can't get me 'ead down these days without rescuin' people or
foilin' robbers or sunnink."
         -- It's a wonder dog's life
            (Terry Pratchett, Moving Pictures)

References:

A89: Archive memory

From: "Filipe Soares Pinto" <filipepinto@mail.telepac.pt>

A89: Re: Archive memory

From: "Bryan Rabeler" <rabelerb@pilot.msu.edu>

Re: A89: Re: Archive memory

From: "Brad O'Dell" <brodell@gte.net>

Prev: A89: Re: Re: Back to arrays... =(
Next: (Non-89) RE: A89: man, this list is becoming just a big joke.
Index(es):
- Main
- Thread