tejekion, We can port BBS programs from the C64 without too much trouble once we have a good working BASIC. I can basically write it in Fortran especially if I provide a POKE and PEEK implementation (non-standard) that has long addresses and up to 16 bit data value. There is also some BBSs written in assembly so in theory, they can be modified for 65c816. PLEASE NOTE: In Assembly language, you are not compiling the program. You "assemble" which would take your ASCII source and assemble them to binary value. A goal for an ML Monitor would be so you can plug in actual ML instructions in hexadecimal format just like found on the Commodore 128 and the Plus/4 when you type Monitor. That's the basic goal on that front. This means you will want to learn the ML hex value for EACH Opcode in the particular addressing mode. In assembly, they may have the same mneumonic but with actual ML Monitor they are hexadecimal representation of pure binary. In the CPU a long jump to subroutine on the 65c816 would be a different opcode value than a short jump to subroutines even if they had the same mneumonic in assembly. This is old school machine language programming.
tejekion, We can port BBS programs from the C64 without too much trouble once we have a good working BASIC. I can basically write it in Fortran especially if I provide a POKE and PEEK implementation (non-standard) that has long addresses and up to 16 bit data value. There is also some BBSs written in assembly so in theory, they can be modified for 65c816. PLEASE NOTE: In Assembly language, you are not compiling the program. You "assemble" which would take your ASCII source and assemble them to binary value. A goal for an ML Monitor would be so you can plug in actual ML instructions in hexadecimal format just like found on the Commodore 128 and the Plus/4 when you type Monitor. That's the basic goal on that front. This means you will want to learn the ML hex value for EACH Opcode in the particular addressing mode. In assembly, they may have the same mneumonic but with actual ML Monitor they are hexadecimal representation of pure binary. In the CPU a long jump to subroutine on the 65c816 would be a different opcode value than a short jump to subroutines even if they had the same mneumonic in assembly. This is old school machine language programming.