Topics:

• Full Parser of Course Grammar:
  • This was: Project II: Parser.

• Translation of AEs to Quadruples (Project III):
  • Use of temporary locations.
  • Each function of the parser returns an integer. This integer gives the location of a variable that will hold, at run time, the value of the construct recognized by the function.
  • See: Project III: Translate Arithmetic Expressions to Quadruples.

• Translation of Control Structures to Quadruples (Project IV):
  • Translating gotos, using backpatching or two passes.
  • Backpatching quadruples.
  • Translating if-else and while-do constructs (both involving backpatching).
  • See: Project IV: Translate Control Structures.

• Comparison/contrast C/C++/Java:
  • Discuss C, C++, and Java with respect to:
    arrays, structs (or classes)

• Postscript:
  • A 2-dimensional page description language.
  • Allows the font characters themselves to be described algorithmically and manipulated.
  • Provides many good primitives for drawing 2-dim figures.
  • A number of examples: Postscript programs.

• Prolog:
  • Prolog knowledgebase example
    
  • Example Prolog session
    
  • Other Prolog examples
    
  • Prolog Manual
    

Sample Questions:

• About parsers:
  • Given a parser, say what it is doing (and how).
  • Write a parser for a simple example language.
• Translating AEs to quads:
  • Explain how the returned addresses of run-time variables work. (Variables which will hold the desired value at run time.)
  • Given some semantic actions, say how they are working.
  • Given a parser, create semantic actions to do some simple task.
• Translating control stuctures:
  • Describe how the backpatching works.
  • Actually do the translation for some simple example.
• Postscript:
  • Given a simple example program, answer questions about it.
• Prolog:
  • Given a prolog program, answer questions about it.