I've wired in a bunch of the stuff I was working on yesterday, and so now the interpreter code has a bunch of run-time correctness checks. Getting those checks in means that the code is relatively more verbose. It turns out I don't get to flex as hard on Java if I try to actually deliver all of the functionality that the book's code is relying on.
It occurs to me that, if I put in the work to rework things in a... somewhat confusing way, I can fit my "enum" code into the paradigm of my "class" code, and then I'd get access to isinstance checks for enums.
Anyway, I can't do that right now, because I've got too much else that I want to do right now. Hopefully I'll get it all together tomorrow. I'll at least try to plan things out after I post this. Once this is either implemented or scrapped, I'll try to get into the parser. I'm not ready to mess with that yet.
Anyway, best wrap things up over here.