Monday, April 9th, 2007
This is definitely in the double-check department.
This sample version has 80+ opcode variations. My current version has 727 opcode variations (7000+ lines 411kb document for desktops only) created through an automation, and I am slowly verifing opcodes and correcting where nesseary (and yes, there is a lot of nessecity). As is, JSASM can create simple, operable, com files, but the opcode results should be verrified before executing any file.
JSASM will eventually include defines, labels, subroutines, macros, etc. along with utility operations (open, saveas…).
Note this is a view of a very raw work – right now JSASM is very strict, inneficient, and with no built in operational help if you want to jump you’ll need to count bytes and specify target memory locations.
If you want to use this script please let us know.
An interesting experiment. Can anyone think of practical uses?
Posted by Dion Almaer at 9:55 am