Hello, all, I'm going back on a few old programs that happen to contain wads of formatted PETSCII (and screen POKE) graphics. Besides just holding non-printable chars as hex value on .BYT statements or the like, is there any sort of convention for meaningfully representing data that's meant to be rendered on screen (via writing to screen RAM or printing via $FFD2/CHROUT). I know there's been any number of printable representation of PETSCII control codes in magazines and such. I'm looking for recommended techniques for that in assembler files. Hex numbers will certainly compile just fine, but it just turns in to a BLOB that is unlikely to be "meaningful" to the reader. Thanks for pointers to any examples, etc. -ethan Message was sent through the cbm-hackers mailing listReceived on 2015-11-12 20:00:08
Archive generated by hypermail 2.2.0.