Something interesting and nostalgic:
A long, long time ago,
in the time of wooden computers and steel programers,
there was:
BIOS + Debuger in 2kbytes.
Basic interpreter, written on machine code in 5kbytes.
Virtual machine (like Java one :) ) in 371 bytes.
Take a look here: http://members.buckeye-express.com/marksm/6502/ and read the articles. Especially "Memory map..." and the first one for Sweet-16 .
Regards.
A long, long time ago,
in the time of wooden computers and steel programers,
there was:
BIOS + Debuger in 2kbytes.
Basic interpreter, written on machine code in 5kbytes.
Virtual machine (like Java one :) ) in 371 bytes.
Take a look here: http://members.buckeye-express.com/marksm/6502/ and read the articles. Especially "Memory map..." and the first one for Sweet-16 .
Regards.
Steve Wozniak was a pioneer programmer. :)
How small do you think we could code Sweet-16?
How small do you think we could code Sweet-16?
Steve Wozniak was a pioneer programmer. :)
How small do you think we could code Sweet-16?
Do you mean Sweet-16 VM for x86? ;) It does not sense. (Or it have sense because of very small code - 1 byte per instruction? :confused: ) Hm, I remember, that the most great macro assembler for Apple II - "Merlin" was written on Sweet-16. Full IDE, macro power as in MASM in approx 10k. BTW: Look how smooth is the mixing of 6502 and Sweet-16 code.