While I wasn't able to reproduce the issue, I did add in more string tests, some related to unicode handling. The tests are run against the reference driver as well as our own -- this allows us to discover what the reference driver outputs.
This uncovered a bug in how we were handling (or, not handling) the null-terminator character \0, which was then fixed.
Also:
I cleaned up some of the driver's behaviour to make it more readable.
I added a .editorconfig file to force VS to output files without BOM.
This was triggered as a result of issue #51
While I wasn't able to reproduce the issue, I did add in more string tests, some related to unicode handling. The tests are run against the reference driver as well as our own -- this allows us to discover what the reference driver outputs.
This uncovered a bug in how we were handling (or, not handling) the null-terminator character
\0, which was then fixed.Also:
.editorconfigfile to force VS to output files without BOM.