Tonight I spent some time preparing my source files for xas99. To help me identify which file contains each "error", I inserted a line with incorrect syntax such as "LIMI **************filename.a99" at the top of each file. This helped me track down some of the offending lines. (I am used to GenAsm which displays the current copy filename and line number containing the error).
I ran into trouble. xas99 was displaying errors but they weren't following the file copy order. For example, a label error in the sixth file was listed well before errors in the second file. This greatly confused me as I could not figure out where the errors were located without searching each file.
I also noticed that many errors are the result of text placed one space after an instruction or field:
" MOVB @LABEL1,@LABLE2 comment1"
" TEXT 'this is a test line' *comment"
Both generate errors during assembly. If I add another space, these same statements work fine. (Edit: I have found all the single space offending lines)
I also am having some trouble with JMP/JGT/JLE/etc. xas99 is telling me that jumps are out of range. The same code assembles properly on real hardware. Are the jump limits too restrictive?
I tried to compare object files between xas99 and real hardware, but finally figured out that xas99 does not generate the object/image if there are errors
Edited by InsaneMultitasker, Sat Jun 24, 2017 2:11 AM.