-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME.txt
70 lines (64 loc) · 2.34 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
Syntactic Analyzer For Tiny C
Copyright © 2014 Mario J. García
=========================================
=========================================
+ IMPORTANT +
=========================================
The implementation using a dynamic
structure can be found in:
github.com/JacobGarcia/SyntacticAnalyzer
(branch DEV). Consider that the DEV
version does not print the type of
variable in the symbols table
=========================================
+ USEFUL NOTES +
=========================================
The source code, version changes, and
more information about the project can
be found in:
github.com/JacobGarcia/SyntacticAnalyzer
(branch MASTER)
=========================================
+ CONTRIBUTORS +
=========================================
Mario Jacob García Navarro - A01363206
=========================================
+ IMPLEMENTATION PROCESS +
=========================================
Different grammar rules were developed
with the purpose of simulate the
behaviour of a syntactic analyzer for
Tiny C, a subset of the C language
-----------------------------------------
IMPORTANT CONSIDERATIONS
-----------------------------------------
Take account that this only is a
lexical and syntactic analyzer for a
(Tiny) C program. Therefore, if the
input program by any means is not valid
or has invalid semantic definitions,
the analyzer will ignore them.
=========================================
+ HOW TO BUILD THE EXECUTABLE +
=========================================
------------------------------------------
make
------------------------------------------
When the build is executed, the c program
file must be passed as an argument:
NOTE: Consider for the next command
that the test file must be in the same
folder. If that were not the case, then
add the file address.
-----------------------------------------
/.scanner < test.c
-----------------------------------------
-----------------------------------------
ADDITIONAL NOTES
-----------------------------------------
The -y flag for the Bison program
basically overrides the file name when
it's generated. Leaving it simple as
"y". The -d flag instead, creates a
header file which can be included in the
Flex source file.