Re: A86: asaps

Re: A86: asaps

• To: assembly-86@lists.ticalc.org
• Subject: Re: A86: asaps
• From: Stephen Hicks <shicks@mindspring.com>
• Date: Tue, 31 Mar 1998 15:34:49 -0500
• Delivered-To: assembly-86-outgoing@towerguard.unix.edu.sollentuna.se
• References: <3521423E.16008437@mindspring.com> <35214E86.A0ACA186@eden.rutgers.edu> <35214FF0.B5C93FFD@mindspring.com> <35215054.4944D846@eden.rutgers.edu>
• Reply-To: assembly-86@lists.ticalc.org

not quite understanding this...  (working on parameters right now...)

do you mean put the program name into asapvar (ld (_asapvar),"asaptrig")?
then, in asaptrig, something like this:

eosld:
 .dw Code

Code:
 blah blah blah
?

Dux Gregis wrote:

> You can store it at the end of your program.  If you load the right name into
> _asapvar, the whole program will be loaded into _asm_exec_ram whenever an asap
> occurs.
>
> Stephen Hicks wrote:
>
> > This isn't quite in response to this thread but it pertains to it, so i'll
> > keep the name...
> >
> > Anyway, where is a good place to install assembly code for asaps?
> >
> > --
> > Stephen Hicks
> > mailto:shicks@mindspring.com
> > ICQ:5453914
> > IRC:Kupopo



--
Stephen Hicks
mailto:shicks@mindspring.com
ICQ:5453914
IRC:Kupopo

• Re: A86: asaps
• From: Dux Gregis <assets@eden.rutgers.edu>

• A86: asaps
• From: Stephen Hicks <shicks@mindspring.com>
• Re: A86: asaps
• From: Dux Gregis <assets@eden.rutgers.edu>
• Re: A86: asaps
• From: Stephen Hicks <shicks@mindspring.com>
• Re: A86: asaps
• From: Dux Gregis <assets@eden.rutgers.edu>

• Prev: Re: A86: asaps
• Next: Re: A86: asaps
• Index(es):
  • Main
  • Thread