08-01-2015, 11:27 AM
Darkstar Wrote:Another example of Excecution Order File.
The method to reset the machine now is randomize usr 0 or even print usr 0 but the first method pulls in the randomize library and the print method pulls in the 1K print routines and maybe I
have custom print routines written in asm. I could always do ASM JP 0 END ASM but that both forces me to do ASM level coding and the start address of zero is perhaps not the same for
every machine if it excludes the Z80 processor.
How do we fix this?
Simple, we just add the keyword RESET to the language.
But this is just execution, there is no order or file.
It appears to be so but you would be wrong for thinking that.
RESET, then it looks for the platform or the format or the ZX in this case and then it does file or to confirm the reset routine for that platform (JP 0) by looking it up in a list or a file and then to
connect it in the right place or to pull it inline.
This way, the platform dependent routines can be kept seperate from the concept of a reset.
This is another way to look at encapsulation.
you can contribute a macro RESET
Code:
#define RESET ASM \
RST 0 \
END ASM
I think it's better to do this rather than expanding the language (cost more, compiler - arch dependant, etc).
This is what other languages (e.g. C) did and was a great success. I'm still in the way to change the compiler so people can define and expand the language themselves.