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.

To 1.) its a superset and no not everything public should be accessible(yes, and with good reason): One thing that I wouldn't like to be accessible is public javascript functions: they can't be executed from cps and they serve no purpose when carried around in cps. Then, I don't want to be held responsible if any public item in an API can't be used in CPS, hence I define what is accessible in CPS. If something is worthless in CPS or even malicious(?), it shouldn't be accessible, because it causes confusion.
I think from my point of view a whitelist is much better controllable than a blacklist, but I may agree that it is maybe overkill here, because there is no relevance for security. Then we would have to define good rules for blacklisting--functions for example.
Another, reason for this implementation is that it is not only a whitelist, but also a 'mapper', so we have control over the names that appear in cps-code, instead of having to use the names that are in the javascript API.
The example for this is the Vector and the Transform class, both define a javascript array-like interface, namely "length" and numeric properties from 0 to length-1. This is used in a ducktyping fashion, for example, ufojs pens expect points to have an API like this. However, in CPS I mapped the name "length" of a vector to it's magnitude. Also, Vector inherits from a class "Complex" that I adopted for our use, but I did not change it's method names. Complex defines methods like "sin" (instead of "calculateSin") which takes no arguments and returns the sine of the complex number, hence this would be a perfectly reasonable property in CPS to be read from a vector, but changing the API of Vector to have a getter in place of that method may cause problems in other parts of the code.

I'm not saying that I wouldn't ever change these APIs, but I think our timely constraints should not be forgotten at tasks like this. A cps_whitelist property defines a good contract between CPS and the JavaScript API, and in future refactorings, this will certainly be rather helpful.

To 2.) can you give an example how this would look like, I'm not getting the idea.