[Solved] CMSC430 Project 1

The first project involves modifying the attached lexical analyzer and the compilation listing generator code. You need to make the following modifications to the lexical analyzer, scanner.l:

1. A new token _ARROW should be added for the two character punctuation symbol _=>.
2. The following reserved words should be added:

case, else, endcase, endif, if, others, real, then, when

Each reserved words should be a separate token. The token name should be the same as the lexeme, but in all upper case.

3. Two additional logical operators should be added. The lexeme for the first should be _or and its token should be _OROP. The second logical operator added should be _not and its token should be _NOTOP.
4. Five relational operators should be added. They are ₌, _/=, _>, _>= and _<=. All of the lexemes should be represented by the single token _RELOP.
5. One additional lexeme should be added for the _ADDOP It is binary .
6. One additional lexeme should be added for the _MULOP It is_/.
7. A new token _REMOP should be added for the remainder operator. Its lexeme should be

rem.

8. A new token _EXPOP should be added for the exponentiation operator. Its lexeme should be _**.
9. A second type of comment should be added that begins with _// and ends with the end of line. As with the existing comment, no token should be returned.
10. The definition for the identifiers should be modified so that underscores can be included, however, consecutive underscores, leading and trailing underscores should not be permitted.
11. A real literal token should be added. It should begin with a sequence of one or more digits following by a decimal point followed by zero or more additional digits. It may optionally end with an exponent. If present, the exponent should begin with an _e or _E, followed by an optional plus or minus sign followed by one or more digits. The token should be named _{REAL_LITERAL}.
12. A Boolean literal token should be added. It should have two lexemes, which are _true and false. The token should be named _{BOOL_LITERAL}.

You must also modify the header file _tokens.h to include each the new tokens mentioned above.

The compilation listing generator code should be modified as follows:

1. The _lastLine function should be modified to compute the total number of errors. If any errors occurred the number of lexical, syntactic and semantic errors should be displayed.

If no errors occurred, it should display _{Compiled Successfully}. It should return the total number of errors.

2. The _appendError function should be modified to count the number of lexical, syntactic and semantic errors. The error message passed to it should be added to a queue of messages that occurred on that line.
3. The _{displayErrors} function should be modified to display all the error messages that have occurred on the previous line and then clear the queue of messages.

An example of the output of a program with no lexical errors is shown below:

1 (* Program with no errors *)

2

• function test1 returns boolean;
• begin
• 7 + 2 > 6 and 8 = 5 * (7 4);
• end;

Compiled Successfully

Here is the required output for a program that contains more than one lexical error on the same line:

1 Function with two lexical errors

2

• function test2 returns integer;
• begin
• 7 $ 2 ^ (2 + 4);

Lexical Error, Invalid Character $

Lexical Error, Invalid Character ^

• end;

Lexical Errors 2

Syntax Errors 0

Semantic Errors 0

You are to submit two files.

1. The first is a _.zip file that contains all the source code for the project. The _.zip file should contain the flex input file, which should be a _.l file, all _.cc and _.h files and a makefile that builds the project.
2. The second is a Word document (PDF or RTF is also acceptable) that contains the documentation for the project, which should include the following:
   1. A discussion of how you approached the project
   2. A test plan that includes test cases that you have created indicating what aspects of the program each one is testing and a screen shot of your compiler run on that test case
   3. A discussion of lessons learned from the project and any improvements that could be made