New answers tagged

0

I wrote a python script which displays error information possibly included in .d64 files that I just published here: https://gist.github.com/thierer/2595e8e28a01111d785f282eac2ac8c5


0

It's probably just a case of two separate engineering teams solving a problem at different times or just not talking to each other. Graphics guys worked out the easiest route for them, software kernal/basic team used their encoding - later on - someone merged the two with a lookup. My guess is its just historical C64 wasn't going to change 'anything' for the ...


8

Your source is most likely in ISO 8859-1 (or -15) encoded (*1), so the compiler has to do code conversion between character literals in your source and the designated target. Without a specifying a target CL65 uses, unlike all other tools, the C64 target by default (*2). As specified in target.c line 193, the C64 Target uses the PETSCII table at line 113, ...


2

I would expect that the CC65 compiler, like most compilers, would output string literals using whatever sequence of bytes appears in the source file. If you want to ensure that particular byte values get included in a string, you can use a backslash followed by a three-digit octal number to include any byte value within a string. While one could use fewer ...


Top 50 recent answers are included