BluPhoenyx wrote:
Michael J. Mahon wrote:It's going to be near impossible to beat the space efficiency of an interpretive system. Small "code" size was a primary design objective for microcomputer BASICs. So, is your problem that the program you want to run is very large (in which case, as Paul points out, a compiler is not the answer)? Or very slow? If it's slow, then it is quite likely that a very little bit of machine code would do wonders to speed it up. Applesoft can CHAIN programs quite nicely, too.An interesting alternative for speed and space would be ProBasic from Beagle Bros. This modular Applesoft is incredibly powerful and versatile for many programming tasks. One creates modules from either Applesoft or Machine language and/or incorporate external modules (as available). Speed is automatically increased by reducing the number of program lines in each module.
Not sure I know what you mean. A program must always execute all the statements called for by the control flow, regardless of modularization. Changing module size could only *add* to the number of module crossings required to execute a program, never subtract. -michael NadaNet networking for Apple II computers! Home page: http://members.aol.com/MJMahon/ "The wastebasket is our most important design tool--and it's seriously underused."