Totally great observation. Chained syntax won’t work this way. You will want to create a ParseExpressionStatement() function which gets called after checking all possible statements. It will simply parse a expression then expect a semicolon. No expressions therefore would need the check for semicolons.

I actually (somewhat) managed to do what you described (making sure assigning variables means you need an ending semicolon), i did in C#, for my programming language, it works well (atleast on the tests ive done) Although its in C#, here is the basic steps; In your Parse, go to your parse_primary_expr(), and before checking for token types and all, add this statement; (C#) if (currentToken == TokenType.SemiColon && tokens[tokens.Count - 1].Type == TokenType.EOF) { this.eat(); return null; } then in the Interpreter, go to the evaluate function, and add a null check at the start, if astNode is null, return null; if (astNode == null) { return null; } and that should be it! This should allow you to force ending semi colon while allowing chaining of variables, (I will re-edit if i missed something)

Think of a line of code where you do print(“hello”); This is an expression with a semicolon. This is what we call an expressionStmt. The point of this is to allow statements with just expressions. If we didn’t have such statements then checking for semicolons would be tricker. Also it allows us to do shorthand if statements or for loops since we just require any statement after the condition.

I guess if you want something like `foo = bar = baz = 5` work, then it gets parsed kinda like `foo = (bar = (baz = 5))`, which indeed means that `baz = 5` has to return 5 in order for `bar = ...` to work. I think some languages use this when doing something like `while (line = readLineFromFile()) { ... }` where the `=` both assigns the read line to `line` and then gives it to the `while` keyword, which either continues in the loop or breaks out of it.

@@mariansam_was_taken thank you! Come to think of it I believe that was explained in the video. Guess it just takes me a bit more to keep up.

Then you need to change the error. I like semicolons hence why I am requiring them here. However if you don’t want them you don’t need them.

or variables rather... kinda defeats the point of it being a "literal" lmao

Hey your the one who is clearly vested in giving feedback and I’m appreciative however if you keep writing comments calling my approach silly I will simply ignore you. This is literally what some languages do. They don’t have a AST node for true or false as those are simply there own thing. So before you critique time for doing so be sure you don’t look like a idiot as this is what some notable languages have done in their AST generation. Hell common C compilers do not differentiate between these just like I have. It’s much more work to create a NullLiteral, BooleanLitersl AST node then simply adding three lines in the a type checker. You could simply define true and false as Booleans and be fine.