Joshua Warner

The first point is easy. Funny how I just introduced a function like that :). When I'm debugging, I specifically don't want anything catching an assert except for my debugger...

Keep in mind that the javac compiler normalizes all strings to UTF-8 (that's how they're encoded inside the class files). Avian maintains either a UTF-8 or UTF-16 internal encoding for...

The class files don't maintain any information about how the source file was encoded. If the output encoding happens to line up with the input encoding, that's just a coincidence....

@bigfatbrowncat, would you mind if I close this?

@duanyao, true, but that doesn't give us much; that only deals with unicode formats (which aren't _that_ difficult to encode anyway), not arbitrary code pages. Also keep in mind that...

If we make that assumption, then it's only useful to us on windows anyway, because Avian's internal strings are (mostly...) UTF-16, to be compatible with Java. I wouldn't be too...

Ah, I see. `setlocale` could work - but it might be hard to get "right", given the non-local nature of the operation. I'd be happy to review/accept patches in this...

One of the things we get with the current tests, that I don't want to lose, is the ability to debug low-level jit issues using the tests. If we have...

@mikehearn, my first suggestion would be to try running it under valgrind. (if you're on Maverics using homebrew, you'll have to install with 'brew install --HEAD valgrind')

Ah, and apparently there's a patch you MAY still have to apply. See https://github.com/Homebrew/homebrew/issues/23660. Specifically, editing the formula: ``` def patches # v4 of patch for Mavericks support, cf. https://bugs.kde.org/show_bug.cgi?id=326724...