You will be assigned one of the following tasks. Please let me know by Tuesday April 3 any preference you might have. I will give you a definite assignment no later than Wednesday April 4. This phase ends on Sunday April 22.
Be sure to carefully consider what semantic errors need to be detected and reported in the processing of arrays and pointers. When errors are encountered, use the "error TYPE" to denote the existence of the error in the abstract-syntax tree and key on the "error TYPE" to avoid a cascade of errors. This is in addition to issuing an appropriate error message through the message module, of course.
Be sure to carefully consider what semantic errors need to be detected and reported in the processing of these operations. When errors are encountered, use the "error TYPE" to denote the existence of the error in the abstract-syntax tree and key on the "error TYPE" to avoid a cascade of errors. This is in addition to issuing an appropriate error message through the message module, of course.
You should add support to both the semantic-analysis routine ("analyze") and the code-generation routine ("encode").
Be sure to consider semantic errors. When errors are encountered, use the "error TYPE" to denote the existence of the error in the abstract-syntax tree and key on the "error TYPE" to avoid a cascade of errors. This is in addition to issuing an appropriate error message through the message module, of course.
You should add support to both the semantic-analysis routine ("analyze") and the code-generation routine ("encode").
Be sure to consider semantic errors.
Code produced by the class during Phase 2 will be available in ~cs712/public/phase3. I will place code there as soon as I have had a chance to evaluate the Phase 2 submissions. You must build your phase 3 contribution upon this "officially sanctioned" code base.
Comments and questions should be directed to pjh@cs.unh.edu