mirror of
https://github.com/fadden/6502bench.git
synced 2024-12-02 13:51:36 +00:00
3368182e14
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) |
||
|---|---|---|
| .. | ||
| WpfGui | ||
| AsmAcme.cs | ||
| AsmCc65.cs | ||
| AsmMerlin32.cs | ||
| AsmTass64.cs | ||
| AssemblerConfig.cs | ||
| AssemblerInfo.cs | ||
| AssemblerVersion.cs | ||
| GenCommon.cs | ||
| IAssembler.cs | ||
| IGenerator.cs | ||
| LabelLocalizer.cs | ||