[A83] Re: allocating uninitialized memory? + _insertmem

[A83] Re: allocating uninitialized memory? + _insertmem

• To: assembly-83@lists.ticalc.org
• Subject: [A83] Re: allocating uninitialized memory? + _insertmem
• From: Tijl Coosemans <tijl@ulyssis.org>
• Date: Sun, 1 Jun 2003 10:42:28 +0200
• In-Reply-To: <001001c327c9$8dbb7bd0$01891581@BSTERNERL>
• References: <000b01c32747$2acd8860$6401a8c0@devbox> <Law11-F49MRmuhXuWDZ0003f87d@hotmail.com> <5.1.0.14.0.20030531093607.00a51550@pop.comcast.net> <003701c327b2$0c492cd0$62f9c594@SOFTIE> <001001c327c9$8dbb7bd0$01891581@BSTERNERL>
• Reply-To: assembly-83@lists.ticalc.org

On Sat, 31 May 2003 19:08:31 -0400, Brandon Sterner wrote:

> how about opening an edit buffer?  i don't believe these modify the
> vat, they simply keep you from creating or removing variables, pushing
> or popping anything on fp or op stacks.  Then you'll have all the free
> ram on the calc to work with.  you wouldn't be able to use absolute
> addressing on this ram though.

I haven't really looked into edit buffers, but don't you have to open
them on existing variables? Maybe even only programs?

• [A83] Re: allocating uninitialized memory? + _insertmem
• From: "Patai Gergely" <patai_gergely@fastmail.fm>

• [A83] Re: allocating uninitialized memory? + _insertmem
• From: Brandon Sterner <bms9019@rit.edu>

• Prev: [A83] Re: allocating uninitialized memory? + _insertmem
• Next: [A83] Re: allocating uninitialized memory? + _insertmem
• Index(es):
  • Main
  • Thread