Can I force ca65 to error if a charmap character is not mapped?

So, let's say I have a charmap mapping like this:
And I then write code like this:
This will cause ca65 to emit assembly like this:
So for '1' it uses the ASCII code for the number 1. But what I would really like it to do is to throw a compilation error.

I tried .feature force_range, but that doesn't do anything (because it seems unrelated to charmaps and just be generally about restricting what goes into a .byte?).

So, I wonder if there's a way to tell ca65 to forget everything about ASCII and require every character to be charmapped?

Statistics: Posted by MenhirMike — Mon Jun 10, 2024 5:51 pm — Replies 0 — Views 47

---