Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!coplex!disk!corpane!herman
From: herman@corpane.uucp (Harry Herman)
Newsgroups: comp.sys.handhelds
Subject: Re: M/L Interrupts/Concurrent Routines
Keywords: ml, interrupts, concurrent routines
Message-ID: <1991Apr23.115645.9250@corpane.uucp>
Date: 23 Apr 91 11:56:45 GMT
References: <28106e62: 2851comp.sys.handhelds@hpcvbbs.UUCP>
Organization: Corpane Industries Inc.
Lines: 17

In <28106e62:2851comp.sys.handhelds@hpcvbbs.UUCP> akcs.scotty@hpcvbbs.UUCP (SCOTTY THOMPSON) writes:

>HP48SX users, has anyone fiddled with interrupts on the HP48SX?
>I would be very interested in being able to have interrupt-driven
>subroutines remaining "memory resident" (such as a sprite animation
>program).  This could facilitate GEM-type interfaces, an entire sprite
>animation library (unattended graphics animation), picture overlays, etc.
>I'd be very interested....10Q.  Scott.


Are you sure you can do this?  I thought all objects in HP48 memory were
subject to being shifted to new addresses whenever garbage collection
occured.  If you wrote something like this, how would you know where your
memory resident routine was located when the interrupt came in.

					Harry Herman
					herman@ukma!corpane