pfirpfel / iml-compiler Goto Github PK

The constructors are inconsistent in using (line, attribute) and (attribute, line) this should be fixed.

Scanner-Output

YEAR MAN!!!! Lueg der de Kranki scheiss ah... hans no sowit gmacht das mer chönd bugfixe

see IML v3 slides

genrate an ParseTree (ITokenList) from IML-Code

– Is any store initialized before it is read or assigned to?
– Are there only initializations of uninitialized stores?
– etc.

I see a need for consistent code formatting. Checkstyle would allow to see what was actually changed in a commit.

bitte überprüfen ob der Abstract Syntax Tree so ist wie er sein sollte

create a bunch IML code samples for testing
all language constructs of IML should be covered

create an AbstractSyntaxTree class with all its member classes and objects according to script

• Is any applied identifier declared?
• Is any identifier (in a single namespace and scope) not declared more than once?
• etc.

– is there no assignment to an in-flow reference parameter?
– is there an initialization of an out-flow parameter?
– etc.

Keyword got renamed...
see slides IML v3

Are there no assignments to constants? etc

generate an AbstractSyntaxTree from the ParseTree

is there any procedure call with one and the same reference supplied to more than one reference parameter?