monasca-analytics/monasca_analytics/banana
Joan Varvenne 7986ab2466 Fix crash when there's no connection in the banana file.
Change-Id: I4e587316e51eb4f9485624a7e35bfc69ffe3b7e4
2016-09-21 15:22:26 +01:00
..
bytecode Add the test back and include BytecodeAssembler in tree. 2016-07-05 11:11:34 +01:00
cli This commit introduces the first version of Banana configuration language. 2016-08-22 14:29:26 +01:00
deadpathck Fix crash when there's no connection in the banana file. 2016-09-21 15:22:26 +01:00
eval This commit introduces the first version of Banana configuration language. 2016-08-22 14:29:26 +01:00
grammar This commit introduces the first version of Banana configuration language. 2016-08-22 14:29:26 +01:00
typeck This commit introduces the first version of Banana configuration language. 2016-08-22 14:29:26 +01:00
README.md This commit introduces the first version of Banana configuration language. 2016-08-22 14:29:26 +01:00
__init__.py Add the test back and include BytecodeAssembler in tree. 2016-07-05 11:11:34 +01:00
emitter.py This commit introduces the first version of Banana configuration language. 2016-08-22 14:29:26 +01:00
pass_manager.py This commit introduces the first version of Banana configuration language. 2016-08-22 14:29:26 +01:00

README.md

Banana configuration language

This module contains everything related to Banana. In each sub-module (sub-folder) you will find a README.md file that describes:

  • Purpose of the module.
  • The current status of the implementation.
  • How testing is done.

The compiler is split in passes. Each pass performs some transformations and / or generates more data. Only the last step has side-effects on the Monanas instance.

Each sub-module roughly maps to one pass run by the compiler.

Passes

The Banana compiler runs the following passes:

  • parse, parse the input and build an AST.
  • typeck, type check the input.
  • deadpathck, remove dead path in the connections.
  • eval, evaluate the AST generated.

Each pass makes some assumptions about the state of the data, and in particular that the previous passes have run successfully. While this is made obvious by the arguments required to run some passes, it is less so for others.

Generally, things to remember:

  • Changing the ordering of passes is more likely to break things.
  • New passes are free to modify the AST / TypeTable.
  • New passes should not break invariants.

For more information on passes, have a look in their specific README.md file.