senior_falcon Posted May 2, 2021 Author Share Posted May 2, 2021 (edited) I have no doubt that a good programmer could write a program that goes directly from an XB program to a finished compiled program that is ready to run. Windows would have plenty of power to do this. On the TI99 it could probably be done if you used SAMS. There are several reasons my compiler works the way it does. 1 - I'm not that good a programmer a good enough programmer to do that. 2 - most of this was developed on a real TI99 with the usual 32K memory limitations. 3 - because of the memory limitations I chose to save the XB program in merge format. This way each line can be read individually and processed. 4 - The compiler reads the XB merge file to make a DV80 file containing "threaded code." This way you can look at the code produced to see if it makes sense and if runtime routines can be made to process it. 5 - now the runtime routines can be created to process the threaded code. Because the compiled code and runtime routines are text files they can be read easily which facilitates debugging. 6 - Since they are source code they must be compiled into object code. 7 - Now the compiled object code must be loaded. This is a little tricky because the code must be able to run in both XB and EA5. So there are custom loaders to handle the various possibilities. Edited May 6, 2021 by senior_falcon 5 Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.