Project 5 -Implement a symbol table

Project5

Description:
This is a team project that build on the previous project. In this project, you are required to implement
a symbol table, and perform every basic semantic error checking listed below:
 undefined type/variable/function names
 redefined type/variable names.
All other semantic errors will not be covered in this project.
Classes in this project
Several classes are defined in different namespace for various purposes. Here is a short explanation of
each class.
 Class absyn::Absyn and all its children are used to define types of nodes in the abstract syntax
tree.
 Class template symbol::SymbolTable provides the implementation of symbol tables used in
this course.
 Class types::Type and all its children are used to represent types supported by tiger languages.
We are not going to use them in this project. But we need them to make sure the syntax is
correct, and no change is needed for the next project.
 Structure symbol::SymTabEntry provides information that should be tied with a
variable/function/type name in the SymbolTable. The SymTabEntry contains three
information: the level of associated name in the source program, a pointer to the type
information of the name, and a pointer to the AST node that contains the
variable/function/type.
 Class symbol::Env provides the compile environment for Tiger language. It has two member
data of symbol::SymbolTable<SymTabEntry, one to store variable/function information,
and one to store type information as specified by Tiger language manual. Its constructor will
insert all global functions like print, ord into variable symbol table, and built-in data types
like int, and string into type symbol table.
 Class semantics::TypeChecking provides functions to check semantic errors at each node in
the abstract syntax tree..
Your major task is to complete the implementation of the following classes.
1. SymbolTable: this class define a class template for symbol table
2. TypeChecking: this class performs the basic type checking using the symbol table
You should not modify other classes in the project.
Tips:
1. Tiger.tab.hh, Tiger.tab.cc, lex.yy.cc files are provided by instructor in SymbolTableProject. So
you don’t need to use your own tiger.ll or tiger.yy files in this project. When you compile the
solution, please just build the MainDriver project.
2. Every time an item is inserted into the variable or type symbol table, a SymTabEntry object
should be construct. In this project, please pass NULL to the second parameter when
constructing a SymTabObject. Let d be a pointer to an absyn::VarDec object, the following
statement will insert it into the variable symbol table:
insertVar( d-getName(),
symbol::SymTabEntry(
env.getVarEnv()-getLevel(),NULL,
d)
);
where insertVar function is provided in the class semantics::TypeChecking
Test Report:
In this project, implementation of the project and test case design can be performed simultaneously.
Don’t wait too long to design test cases. In this project, please provide a tiger program called: test.tig
to cover all of the following scenarios:
 Two variables with the same name are defined at the same level.
 Two types with the same name are defined at the same level.
 Two functions with the same name are defined at the same level.
 One variable and one function with the same name are defined at the same level.
 Two variable with the same name are defined at the different nesting levels.
 Two types with the same name are defined at the different nesting levels.
 Two functions with the same name are defined at the different nesting levels.
 One variable and one function with the same name are defined at the different nesting levels.
 An undefined variable is used
 An undefined type is used
 An undefined variable is used in function parameter list
 An undefined function is used
Important Dates and Deadlines:
Monday Tuesday Wednesday Thursday Friday Saturday Sunday
6 (Nov.)
Project
assigned
7 8 9
1st time log
report due
10 11 12
13 14 15
2nd time log
report due
Test.tig due
Alpha
version due
16 17
Test Report
due
3rd time log
report
18 19
20
Project Due
day
15 16 17 18 19 20
Notes:
 All reports/files are due at 4:00am on the due day.
 Each team is required to submit 3 time log reports.
Instructor provided files in the class repository
The following files are provided by the instructor:
 SymbolTableProject folder. This contains a sample Visual Studio 2010 project.
 Description5.pdf: this file
 Rubric5.doc: the rubric used to grade this assignment.
 example.txt. sample output
 Testreport.doc: format of testing report for this projectHow to submit
1. Once you have finished, submit the project in the following way:
 Group leader needs to make sure files and reports are placed in the right folder, and have
been pushed to the master repository in ranger.
 Put test case, test report under Testing folder
 Put alpha version of TypeChecking.cpp and SymbolTable.cpp under
AlphaVersion folder
 Put timelog reports under Timelog folder
 Leave the final version under folder SymbolTableProject folder
 Any commit of the project after the deadline is considered as cheating. If this
happens, the latest version before the deadline will be graded, and you may receive
up to 50 points deduction.
 Each team is required to submit hard copies of the following files. Please put copies
of these files in a folder/envelope of size 9 x 12. You can buy folders from lab
assistant at KOM 351.
 testing report
 test.tig
 3 timelog reports
 SymbolTable.cpp (alpha version)
 TypeChecking.cpp (alpha version)
 SymbolTable.cpp (final version)
 TypeChecking.cpp (final version)
Write down team number, and names of all team member on the cover. Give the
folder/envelope to the instructor at the beginning of the class on the due day.
You can check your overall grade by pull rubric3.doc from the master repository after the notice from
the instructor.