tomascartman/compiler

A compiler project to compile a language proposed by some teachers for the learning of the process of compilation

Welcome to my github profile

My name is Marco and i'm a computer engeneering student.
Right now i'm learning web programming, like JS and its main frameworks, Node.js and others.
I also like mobile programming with Kotlin to Android.

Other medias that i use

compiler's Issues

Create tests

Create tests to verify if the code is doing what it should be doing without a human (and human mistakes).

Escape characters in input file

When the input file is read, the caracters that should be of escape like '"' or '\n' are put on the list of strings (sourceCode) like '' and '"', this is a problem to some automatons, in specific the AutomatonString that handles the char '"'.
Because it's already in the list of strings, it will be read once char at time, and treated like that, needing a special tratament at the automatons that should handle those escape chars.

The file to read must not have blank lines

After reading the file, trying to use the function nextChar() to access the list one char at time, blank lines in the file causes a java.lang.StringIndexOutOfBoundsException

Problem with three or more relational operators in sequence

There is no problem when two operator are in sequence, like "==" or ">=", but the linguage do not allows three operator in sequence, like "===", this should be a error, in the current code this would be treat like "==" first and then "=", generating two tokens.

Refractor automatons code and lexer code

The automatons should have a function to return a token when asked if it is in a valid state to generate the token. This will remove a lot of "if" code from the lexer, which should not be doing these tests.

A Token class should be created.

Problem to valid token "!="

In the diagram, after the state zero, all the other states are already valid states without a second char, excpet state two, which is represented by "!", it needs to be followed by a "=" like "!=" to be a valid token. it must be decided if the lexer.kt will reset the automaton or the automaton itself will do this job, and so implements and use the operator lookahead to test if after a "invalid" char "!" we can get a valid token "!=" by looking the following char.

Ignore spaces instead of sending to the automatons to test them

It's a simple if before sending a char to the automatons to test if this char is an space.

Error states in some automantons may be necessary

Some automatons can just ignore when the lexeme do not fit on them, but others they (probably) must declare an error, for now i have notice that AutomatonNumbers and AutomatonLogicalOperators should put an error.

AutomatonNumbers when it finish the lexeme with a 'dot', without a number at the end, or when it starts with a 'dot'.
AutomatonLogicalOperators when it get only one '&' or '|' symbol.

I don't know if this error should be task of the Lexer, whom has the next char or somehow the automatons should be responsible for this job. Maybe the lexer reporting an error after 'n' lookaheadChar gets trying the new lexeme will handle this problem