new formulae language implementation

unified language and parser for the registered types  'vector' and 'real' and @dictionary parameters
referenceing of values across cps rules/@dictionaries etc
transformation matrices
Polar vector constructor
updated importer that saves onDir and onLength
got rid of a lot old code
etc.

The whole CPS whitelisting thing confuses me. Why are we not simply exposing the object's public interface? There are two underlying questions:

1. Is the public API of the underlying objects a superset of the CPS interface? If so, why? Shouldn't one be able to access everything in CPS that one can access from the public API?
2. If the answer to question 1 is "yes, and with good reason", then why not just cast the objects to a superclass which does correspond to the CPS API?