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
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
|
Documentation
=============
In total the documentation burden is (at most) 1000 words
plus one diagram. Assesment of the documentation is not relative
to compiler functionality, it just requires a description
of the compiler as-is, and a realistic assessment of the
compiler's strengths and weaknesses.
AST
===
Overview Diagram
----------------
_Add a diagram of your AST, which is designed to *usefully* communicate
the *important* properties of the AST._
- _Use whatever level of detail you feel is appropriate_.
- _You do not need to include every part of the AST, and you
don't need to include every class_.
- _Zooming should not be necessary to understand it_.
The file should be called `my-ast.png`. The software used
to generate the png is up to you, or you can draw it by hand
and scan it if you wish (though beware the eventual file-size).
Description
-----------
_Describe the structure and organisation of your AST in 200 words
or fewer_.
- _Feel free to refer to your diagram_.
- _Try to capture the most important properties_.
- _You can use code, but it is included in your budget_.
I used a pure abstract Node class as an entry point to the AST, so that I could print
it out using the `Bindings printAsm(Bindings, int &)` method.
Strengths
---------
_Give two strengths or capabilites of your AST, using 50 words or less for each one_.
### Strength 1
_50 words or less_
### Strength 2
_50 words or less_
Limitations
-----------
_Give two limitations of your AST, using 50 words or less for each one_.
### Limitation 1
_50 words or less_
### Limitation 2
_50 words or less_
Variable binding
================
General approach
----------------
_Describe your overall approach to mapping variable, parameters, etc.
into registers or memory locations at exection time, using 200 words
or less_.
- _how did you manage registers?_
- _did you use the stack?_
- _is there a function or API for managing and looking up bindings?_
_200 words or less_
Strengths
---------
_Give two strengths or capabilites of your binding approach, using 50 words or less for each one_.
### Strength 1
_50 words or less_
### Strength 2
_50 words or less_
Limitations
-----------
_Give two limitations of your binding approach, using 50 words or less for each one_.
### Limitation 1
_50 words or less_
### Limitation 2
_50 words or less_
Reflection
==========
Strengths
---------
_What two aspects of your compiler do you think work well (beyond
those identified in the AST and binding parts)?_
### Strength 1
_50 words or fewer_
### Strength 2
_50 words or fewer_
Scope for Improvment
---------------------
_What parts of your compiler do you think could be improved?_
- _This is not looking for things like "It should support more C constructs". What
would you need to do or change in order to support those things?_
### Improvement 1
_50 words or fewer_
### Improvement 2
_50 words or fewer_
Functionality (not assessed)
============================
Which of these features does your compiler support (insert
an `x` to check a box):
1 - [x] Local variables
2 - [x] Integer arithmetic
3 - [x] While
4 - [x] IfElse
5 - [x] For
6 - [x] Function calls
7 - [x] Arrays
8 - [x] Pointers
9 - [x] Strings
10 - [ ] Structures
11 - [ ] Floating-point
Note that all features will be tested, regardless of what
appears here. This is documentation of what you expect to work,
versus what doesn't work.
Feedback (not assessed)
=======================
_What aspects of your compiler would you like feedback on.
Be specific, as "what could I have done differently" is
too general to answer._
### Feedback 1
_20 words or fewer_
### Feedback 2
_20 words or fewer_
|
