UTFException overrides toString (without parameters), and does not override the toString which uses the sink.
The odd result is, if you catch a UTFException, you get different behaviors for:
writeln(e);
writeln(e.toString());
The first prints e.msg with source file and line number where the exception was thrown, and then the stack trace.
The second prints a customized message for UTF, but no stack trace, and no filenames or line numbers.
These should be consistent, and an exception message should be useful for finding the source of the error (printing no file name or line number is a terrible default behavior).
Comment #1 by robert.schadek — 2024-12-01T16:36:36Z