horsecz/fit-ifj-teamproject

IFJ Project - Language Go, FIT@BUT 2020

fit-ifj-teamproject's Issues

Tests

We should prepare some test for every part of our project

• Scanner
• Parser
• Semantic Analysis
• Code generator
• Symtable
• ...

Also, it may be good to figure out how to use https://gitlab.com/kam29/ifj-testsuite and apply it to our project.

Wrong flags in makefile

In makefile some parts (ex.: scanner.o) have $(CFLAGSS) even when they should be $(CCFLAGS). Is this expected behavior you have reason for? In other case could you / or should I repair it?

Also I'd like to add some kind of DEBUG make to makefile with -D DEBUG option.

Missing project files

I know this is not needed now, but it'll be good, if the issue would be here later.

We need create these files:

• rozdeleni -> file reflecting how many % of points each team member gets from this project (in format: xloginXX:NN\n where NN is % amount of points)
• rozsireni -> reflecting which extensions we have implemented (in format EXTENSION_NAME\n)

Create file structure

We should consider creating a file structure for this project along with some deployment scripts that will take files from our file structure and prepare them for submission.
Something like this maybe.

/
|- README.md
|- Makefile
|- ifj2020.c
|- ifj2020.h
|- doc/
|  |- scannerAutomaton.graphml
|  |- LLTC_LL_grammar.xml
|  |- LL_grammar.odt
|- src/
|  |- (all src files here - scanner.c, scanner.h, etc..)
|- tests/
|  |- (all tests that we created)

Documentation

We will need to create documentation for our project.

My recommendation would be probably using MD on GitHub Wiki and then download this as a PDF but I'm not sure if this is doable or if this is even the best course of action for creating documentation.

Also please do follow Doxygen standards for creating comments in your header files and other source files.
I'll push Doxyfile shortly - use doxygen doc/doxyfile to generate documentation based on Doxygen (use in . directory)

This issues is a lower priority compared to others as it'll be needed for project defense mainly but probably should also be included in the final submission (to check this please refer to project assignment)
TODO: This issue is WIP and will be modified.

Unused function statementMul()

In parser.c there is unused function statementMul. It probably has to be used but I forgot to place it somewhere. This may result in broken grammar and not correct syntax analysis.

Symbol table

According to yesterday's IFJ lecture, we need to modify our symtable (a lot .. or not?):

1. We need to use more symtables, not just one. Also we need two types of symtables:

• Global symtable: symtable for functions, which contains keys-func names and data as return types, argument types, insider func identificator (for code generator purposes), maybe more (info: last IFJ lecture)
• Symtables for identificators, which contains keys-identificator names (as we have now) and data as datatype (as we have) and maybe more (again: last IFJ lecture, I dont remember everything)

2. Global symtable (for functions) will be just one. Each scope has its own symtable for identificators. (func, if, for, ..)
3. Because of 2), we need other structure, which allows us do some operations (create, destroy, point to symtable, etc.) on symtables. Recommended structure from lecture is stack (of symtables). Also we use stack for pointers in our current symtable, so making it for symtables should't be at least that difficult.