So there is no CI working for it to build off right now and I shouldn't worry about it?

Had to update .arcconfig also in order to land it. Apparently it's not building (although I didn't get an error in terminal, it just errors in the commit). It looks like the build instructions are out of date? Was going to try to fix, but the Jenkins link is giving a 503 error, and I don't see anything in Harbormaster for more recently active projects with different Jenkins information than what Ratscript's has. So I'm not sure what the current status of your build pipeline is. I understand a lot of changes happened since I last touched it.

@jcmcdonald Also just noticed this also never got reviewed.

Let me see if I can remember how to arcanist a minute.

@jcmcdonald was just removing myself from open tasks and apparently this never got reviewed. Not sure what the current state of Ratscript docs is. Is this still valuable?

@jcmcdonald Sorry this took me forever, I kept meaning to but forgot. I assumed names should be alphabetical since the rest of them were but please move me if it makes sense to you. No idea what cohort I technically belonged to 😅

@wdede all the stuff in the _themes directory I copied over from SIMPLEXpress without editing, because something was broken in Ratscript's themes directory and it was an older version anyway; I didn't manually edit any of that. Otherwise I added some of the information from the wiki just to offer a starting point. Nothing that's working now is really good to put in the documentation :/

I would guess you don't want to approve/land this until docs are available, but do you want to include the old PawLIB documentation still, or take it out completely?

• Copy icons from individual project doc folders

The Tokenizing part of this was handled with D383, but the tokens are not yet parsed into a tree for interpretation.

The Tokenizing part of this was handled with D383, but the tokens are not yet parsed into a tree for interpretation.

The Tokenizing part of this was handled with D383, but the tokens are not yet parsed into a tree for interpretation.

Addressed in D383

The work in D383 didn't directly address this, and in following the pattern of Lox, it isn't the Lexer's job to discern patterns, that happens at the next step of interpretation. (Parsing?)

@jcmcdonald Should I close this task or leave it as a parent for further tasks related to console?

Console's main.cpp now does, among other things, call ratscript.hpp/cpp, which calls the lexer. As of D383

Lexer may update as needs evolve but the basics are complete.

• Adjust run_prompt to run in loop instead of single run

I think this is finally ready for review. I know it's super long :( If any of you have time to look over even a file or two at a time, that'd be great! All my tests are passing but I'm insecure about how well I wrote the tests. Totally open to suggestions for more things to test!

• Run format on all cpp and hpp files
• Clean up formatting and comments
• Add and troubleshoot numerical test
• Test non-keyword identifiers and troubleshoot
• Write test for newlines, add COLON to tokentypes
• Add tests for comments, moved comment logic and newline logic to functions
• Add testing for strings and troubleshoot

TODO: Test numbers, non keyword identifiers, newline, comments.

• Adjust outer.mk
• Troubleshoot tests, write more tests

Although there is maybe something else going on with that code, because if I call substr() with two parameters, and the second one is out of range, ie test_str.substr(0, 25) ..... I don't get an error at all, and I probably should. (It instead just returns the original string at the original length)

IOCat isn't quite doing what I want here, but that seems to be an issue with IOSqueak and not with what I've done here; if someone has time to review this (not many changes) so I can get it landed sometime, that'd be great.

• Adjusted outer makefile to make console when using make ready
• Setup test framework, get includes working
• Overload == and != for Token, work on tests

Todo: Fix IOCat commands if working properly, debug line numbers, modify for testing and write tests. Also figure out whether comments are parsing wrong or if I was confused, and fix.

• Stringify tokens, work on debug in lexer