Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
tddd55-lab
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
TDDD55 - Compilers and Interpreters
tddd55-lab
Commits
426bfae8
Commit
426bfae8
authored
1 year ago
by
johti17
Browse files
Options
Downloads
Patches
Plain Diff
Reorganized the README
parent
b16d7eb7
No related branches found
No related tags found
1 merge request
!5
Feedback 2023
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
lab3-4/README.md
+19
-22
19 additions, 22 deletions
lab3-4/README.md
with
19 additions
and
22 deletions
lab3-4/README.md
+
19
−
22
View file @
426bfae8
...
...
@@ -8,28 +8,7 @@ To start, begin by integrating what you did in lab 1 to the `scanner.l` file.
Here it is important that you are careful, and that you do not simply copy paste.
Look at the structure of
`scanner.l`
and enter your rules s.t you do not remove any includes present in that file.
### Testing Lab 3.
There is a number of test files in the
`test`
directory that you may use to check if your parser works as expected.
We also provide traces that you can use to compare the output of your solution to some expected output.
To do this you can exceute the following sequence of commands.
To check if you get about the same result for expressions you can run:
```
bash
./compiler ./test/expression_test.prog
>
my_output.txt
diff
-y
my_output.txt ../traces/trace_expression_test.txt
```
The same procedure can be done for the more advanced test, that is
`traces/trace-lab3.txt`
```
./compiler ./test/test > my_output.txt
diff -y my_output.txt ../traces/trace-lab3.txt
```
A good starting point for Lab 3 is to start by implementing support for the different expressions:
Following this a good starting point for Lab 3 is to start by implementing support for the different expressions:
```
C
/* --- Your code here ---
*
...
...
@@ -71,6 +50,24 @@ condition :
/* --- End your code --- */
```
### Testing Lab 3.
There is a number of test files in the
`test`
directory that you may use to check if your parser works as expected.
We also provide traces that you can use to compare the output of your solution to some expected output.
To do this you can exceute the following sequence of commands.
To check if you get about the same result for expressions you can run:
```
bash
./compiler ./test/expression_test.prog
>
my_output.txt
diff
-y
my_output.txt ../traces/trace_expression_test.txt
```
The same procedure can be done for the more advanced test, that is
`traces/trace-lab3.txt`
```
./compiler ./test/test > my_output.txt
diff -y my_output.txt ../traces/trace-lab3.txt
```
## Lab 4
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment