rmeyer@cca.UUCP (Richard Meyer) (10/16/85)
I am using the TASC Applesoft compiler from Microsoft for a data
analysis program that receives its input from an interrupt driven
routine (written in assembly) that deposits the data in COMMON.
The following problem occurs: As soon as the compiled program
executes a terminal I/O or high-resolution graphic statement
(such as a PEEK to check for pending terminal input, or HPLOT),
the program behaves unpredictably - usually it terminates with a
garbled error message. The same program works just fine if
executed by the Applesoft interpreter, or if the compiled program
turns off the interrupt system during the execution of the 'sensitive'
statements (unfortunately this is not an acceptable solution).
It appears that some of the runtime library routines of TASC interfere
with interrupt processing, though I have no idea how. Base page
conflicts can be ruled out -- the only base page location used during
interrupts is location $45, which is not used by TASC (according to
Microsoft documentation).
Questions:
1. Did anyone have to deal with a similar problem and found a way
around it?
2. Does anyone know the cause?
3. If it is indeed the fault of the compiler, is there another
Applesoft compiler that does not have that problem?