Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site watdcsu.UUCP
Path: utzoo!watmath!watnot!watdcsu!dziegler
From: dziegler@watdcsu.UUCP (Rudolf Shmitt)
Newsgroups: net.micro.apple
Subject: Applesoft Interrupts
Message-ID: <1914@watdcsu.UUCP>
Date: Tue, 26-Nov-85 18:01:07 EST
Article-I.D.: watdcsu.1914
Posted: Tue Nov 26 18:01:07 1985
Date-Received: Wed, 27-Nov-85 05:12:08 EST
Distribution: net
Organization: U of Waterloo, Ontario
Lines: 20



   In order to allow people who do not know assembly
to write interrupt code for a data aquisition system
I am trying to set up a system whereby ( actual
(slow) hadrware ) interrupts can be written in applesoft .
It is important that this code use the same variables
as the main program ( so don't suggest using the two 
address spaces of the IIe/c ) .

   I've tried a simulated CTRL-C with an onerr in
the main program , but was foiled by the microsoft 
HAPPY-CODE ( not to mention needing a ramcard 
which is undesirable ) . My current version maintains
a second zero page for the interrupt ( except for
pointers to variable space ) , and the interrupt 
applesoft sits elsewhere in memory . I am having weird
but persistent problems with this scheme and am looking
for suggestions as to what they might be , or viable
alternate methods .