Handle invalid chars better, and do small cleanups around error output. (#657)

This adds a test for invalid characters (that would've failed before, because the printed char isn't escaped). Not sure if there's a good way to test the PrintDiagnostic code, as it appears to occur on bison parser errors, which I'm just not sure how to trigger.
2026-10-04 22:02:52 +01:00 · 2021-07-20 12:04:45 -07:00
parent 1ddb1a264a
commit 368fc0063c
6 changed files with 23 additions and 14 deletions
@@ -0,0 +1 @@
+�
@@ -0,0 +1,2 @@
+1.1: invalid character '\xFE' in source file.
+EXIT CODE: 1