6502bench/20120-char-encoding-a_cc65.cfg at fa1b0af93295c87330618c97fbd090563ca7d2a4 - 6502bench - Applefritter: Git

6502/6502bench

mirror of https://github.com/fadden/6502bench.git synced 2024-12-02 13:51:36 +00:00

Andy McFadden 3368182e14 Allow single-character DCI strings

The DCI string format uses character values where the high bit of the
last byte differs from the rest of the string.  Usually all the high
bits are clear except on the last byte, but SourceGen generally allows
either polarity.

This gets a little uncertain with single-character strings, because
SourceGen can't auto-detect DCI very effectively.  A series of bytes
with the high bit set could be a single high-ASCII string or a series
of single-byte DCI strings.

The motivation for allowing them is C64 PETSCII.  While ASCII allows
"high ASCII" as an escape hatch, PETSCII doesn't have that option, so
there's no way to mark the data as a character or a string.  We still
want to do a bit of screening, but if the user specifies a non-ASCII
character set and the selected bytes have their high bits set, we
want to just treat the whole set as 1-byte DCI.

Some minor adjustments were needed for a couple of validity checks
that expected longer strings.

This adds some short DCI strings in different character sets to the
char-encoding regression tests.

(for issue #102)

2021-08-08 15:38:39 -07:00

12 lines

271 B

INI

Raw Blame History

 # 6502bench SourceGen generated linker script for 20120-char-encoding-a
 MEMORY {
     MAIN: file=%O, start=%S, size=65536;
 #    MEM000: file=%O, start=$1000, size=1299;
 }
 SEGMENTS {
     CODE: load=MAIN, type=rw;
 #    SEG000: load=MEM000, type=rw;
 }
 FEATURES {}
 SYMBOLS {}