I'll be honest: I don't have two weeks worth of work to talk about this week. I've had trouble getting the work done at all for the past two weeks, but I'm hoping to turn that around and pick up the pace for the rest of the semester. I'm still hoping to have a working parser by the end of Thanksgiving break, at least for the basic version of TweeTeX that we've been working on, so that's what I'm working towards.
From our last discussion, I took your feedback about documentation, doctests, and functions into account and modified the lexer.py and tweetex.py files. I've also linked the TweeTeX github repository in the resources section of the main tutorial page.
I've started writing the recursive descent parser, but I haven't gotten far enough to have any substantial questions or run any examples...I'm refreshing myself of the structure of recursive descent parsers by looking at your example and Crafting Interpreters by Bob Nystrom. I'm following a similar structure as my Lexer code and making a Parser class rather than making a Parser function...I'm not sure if this is the Best thing to do, but it's my instinct and gives the lexer and parser code more of a library feel...
last modified | size | ||
basictweetex.twx | Sun Dec 22 2024 09:16 am | 300B | |
lexer.py | Sun Dec 22 2024 09:16 am | 3.6K | |
tweetex.py | Sun Dec 22 2024 09:16 am | 606B |