# mw-parser A rule parser for MicroWorld ## Part of the overall MicroWorld system While this code works and is interesting on its own, you also need at least [mw-engine](https://github.com/simon-brooke/mw-engine) and [mw-ui](https://github.com/simon-brooke/mw-ui). There will be other modules in due course. You can see MicroWorld in action [here](http://www.journeyman.cc/microworld/) - but please don't be mean to my poor little server. If you want to run big maps or complex rule-sets, please run it on your own machines. ### Version compatibility There are substantial changes in how rule functions are evaluated between 0.1.x versions of MicroWorld libraries and 0.3.x versions. In particular, in 0.3.x metadata is held on rule functions which is essential to the functioning of the engine. Consequently, you cannot mix 0.1.x and 0.3.x libraries: it will not work. In particular the parser in actual use has changed in 0.3.x from the `mw-parser.core` parser to the `mw-parser.declarative` parser. The API of the parser is also substantially revised and is not backwards compatible, so if you have code written to use 0.1.x versions of this library it will need to be modified. I apologise for this. On the upside, the new parser API is much simpler. ## Usage Main entry point is (compile _string_), where string takes a form detailed in __[grammar](#grammar)__, below. If the rules represnted by the string are interpretted correctly, the result will be a a list of compiled Clojure anonymous functions; if the rule cannot be interpretted, an error 'I did not understand...' will be thrown. Each of these functions will have metadata including: * `:rule-type` : the type of rule the function represents; * `:lisp` : the lisp source from which the function was compiled; * `:parse` : the parse-tree from which that lisp source was derived; * `:source` : the rule source from which the parse-tree was derived; * `:line : the one-based line number of the rule source in the source file. The values of `:rule-type` currently supported are: * `:production` : an if-then rule which transforms the properties of a single cell, based on the values of properties of that cell and optionally of its neighbours; * `:flow` : a flow rule which creates flows of values of a numeric property from one cell to other cells. Values which it is intended will be supported include rules to create graphs which will enable the user to aggregate and interpret what is happening in the world. Types which it is envisaged will be supported include `:time-series`, `bar-graph` and perhaps others, but grammar for these has not yet been developed. ### Generated function and evaluation environment The generated function is a function of two arguments + __cell__ a cell in a world as defined in mw-engine.world, q.v.; + __world__ the world of which that cell forms part. It returns a new cell, based on the cell passed. Actions of the rule will (can only) modify properties of the cell; there are two properties which are special and SHOULD NOT be modified, namely the properties __x__ and __y__. ### Execution Each time the world is transformed, exactly the same set of rules is applied to every cell. The rules are applied to the cell in turn, in the order in which they are written in the rule text, until the conditions of one of them match the cell. The actions of that rule are then used to transform the cell, and the rest of the rules are not applied. So, for example, if your first rule is if x is more than -1 then state should be new then no matter what your other rules are, your world will never change, because all cells have x more than -1. If you are having problems because one of your rules isn't working, look to see whether there is another rule above it which is 'blocking' it. ### Grammar #### Comments + Any line which starts with the hash character (#) is ignored; + Any line which starts with a semi-colon (;) is ignored. #### Rules A rule comprises: + if _conditions_ then _actions_ Each rule must be on a single line. There should be nothing else on that line. #### Conditions In rules, _conditions_ is one of: + _condition_ + _condition_ and _conditions_ + _condition_ or _conditions_ Note that 'and' takes precedence over or, so conditionA and conditionB or conditionC and conditionD is interpreted as (conditionA and (conditionB or (conditionC and conditionD))) A _condition_ is one of: + _property_ is _value_ + _property_ is not _value_ + _property_ is in _values_ + _property_ is not in _values_ + _property_ is more than _numeric-value_ + _property_ is less than _numeric-value_ + _number_ neighbours have _property_ equal to _value_ + _number_ neighbours have _property_ more than _numeric-value_ + _number_ neighbours have _property_ less than _numeric-value_ + more than _number_ neighbours have _property_ equal to _value_ + fewer than _number_ neighbours have _property_ equal to _value_ + some neighbours have _property_ equal to _value_ + more than _number_ neighbours have _property_ more than _numeric-value_ + fewer than _number_ neighbours have _property_ more than _numeric-value_ + some neighbours have _property_ more than _numeric-value_ + more than _number_ neighbours have _property_ less than _numeric-value_ + fewer than _number_ neighbours have _property_ less than _numeric-value_ + some neighbours have _property_ less than _numeric-value_ #### About neighbours Note that everywhere above I've used 'neighbours', you can use 'neighbours within _distance_', where _distance_ is a (small) positive integer. A cell has eight immediate neighbours - cells which actually touch it (except for cells on the edge of the map, which have fewer). If the cell we're interested in is the cell marked 'X' in the table below, its immediate neighbours are the ones marked '1'. But outside the ones marked '1', it has more distant neighbours - those marked '2' and '3' in the table, and still more outside those.
3333333
3222223
3211123
321X123
3211123
3222223
3333333
If a rule just says 'neighbours', and not 'neighbours within', it means 'neighbours within 1'; so if some neighbours are scrub then state should be scrub has exactly the same meaning as if some neighbours within 1 are scrub then state should be scrub #### Actions In these rules, _actions_ is one of: + _action_ + _action_ and _actions_ and _action_ is: + _property_ should be _value_ + _number_ chance in _number_ _property_ should be _value_ #### Properties In the above, _property_ is the name of any property of a cell. Any alpha-numeric string of characters can form the name of a property. Actions should __NOT__ try to change the reserved properties __x__ and __y__. #### Values in Conditions Values in conditions and actions are considered slightly differently. In a condition, a value is one of: + _symbolic-value_ + _numeric-value_ The '...more than...' and '...less than...' conditions imply a _numeric-value_. Thus "if altitude is more than fertility..." is interpreted as meaning "if the value of the property of the current cell called 'altitude' is greater than the value of the property of the current cell called 'fertility'", whereas the apparently similar condition 'if altitude is fertility...' is interpreted as meaning "if the value of the property of the current cell called 'altitude' is the symbol 'fertility'". Thus _symbolic-value_ is any sequence of alphanumeric characters, whereas _numeric-value_ is one of: + _number_ + _property_ and _number_ is any sequence of the decimal digits 0...9, the minus character '-' and the period character '.', provided that the minus character can only be in the first position, and the period character can only appear once. #### Values in Actions A _value_ in an action is one of + _symbolic-value_ + _arithmetic-value_ + _number_ where _arithmetic-value_ is: + _property_ _operator_ _numeric-value_ and _operator_ is one of the simple arithmetic operators '+', '-', '*' and '/'. ### Shorthand Note that '...neighbours are...' is equivalent to '...neighbours have state equal to...', and 'some neighbours...' is equivalent to 'more than 0 neighbours...' ### Roadmap The existing parser, *mw-parser.core*, works but is not well written. A much better parser which does not yet completely work, *mw-parser.insta*, is also included for the adventurous. I intend to replace *mw-parser.core* with *mw-parser.insta* as soon as *mw-parser.insta* correctly parses all the test rules. ## License Copyright © 2014 [Simon Brooke](mailto:simon@journeyman.cc) Distributed under the terms of the [GNU General Public License v2](http://www.gnu.org/licenses/gpl-2.0.html)