… most browsers by now
The example input string for Calc had exponentiation instead of multiplication, which caused the interpreter to not recognize the whole string and return the initially confusing answer of 6. This patch makes the string the same as all the others, and gives the result 42.
…easure to stop vandalism :)
…d variable declarations
… to be causing any problems (expr4 takes an argument that tells it whether or not it's ok to accept an empty expression, but OMetaParser's rulePart rule was not passing that argument to expr4)
…ible with memoizeParameterizedRules()
…- this makes it easier to include entire programs in this kind of string
…or OMeta rules. This work was actually done by Page-, but it was too complicated to reconcile my unrelated changes to bs-ometa-compiler.js and bs-js-compiler.js with his, so I couldn't just accept Page's pull request. You can see his original changes here: Page-@7ce37b0#diff-2
…rgot to do this, it only fixed the library functions for escaping/unescaping
…s for its references. This fixes an issue where if you clone the returned object and then run matchAll it runs on the original rather than cloned object.
…egatesTo() in Worlds implementation
…o added def. of fromTo rule to OMeta grammar.
…ur ECOOP'11 paper -- thanks to Aran Lunzer for spotting this problem! (BTW, the new version of the paper on the VPRI website has the new and improved semantics in Sec. 5.3
…StreamProxy, i.e., foreign rule invocation
…rting REPL-type applications
…om being displayed in the workspace