Update worklog 12/26/21

spec.txt

@@ -55,3 +55,18 @@ of cool image and text transition libraries out there. It does mean setting up s
 like, just kill me now
 
 Out of the three of these I think the Java thing would be the easiest and I think the Godot thing would be the best.
+
+12/26/21
+Merry Christmas! Forgot to update this for a bit, but let's talk turkey about what's been done so far. I decided to
+implement this as a C++ project for portibility. I know Java might have technically been more portible, but I'm
+thinking Godot is in the near future for this and Javascript has something like a FFI so I went for a C project
+called "peg/leg" (`man peg` weirdly...) to implement the language. I can't recommend the project, it is not copyleft
+and although the "leg" tool provides a lex/yacc-like interface but it does a terrible job of documenting the peg semantic
+actions, (like how the fuck the * operator works or how to properly use the predicates), and a lot of stuff is straight
+up missing (%nterm, $1, yyin). I like PEGs, but if I could do this again I'd just use flex/bison.
+
+Where to go from here? I could just start integrating this into a Godot project. Right now I'm making a little command
+line driver to test it out. Portibility? This project is gonna be small and I could just use submodules, or just little
+subprojects in the same project for each interface (Web/Godot/Whatever else). At this point I've written so little code
+that I think I could just port it to each project as well. For Godot I'm pretty sure I'll have to integrate it with
+the SCons build that they provide on their website, so I probably can't link to a .so file.