Thanks. It looks to me like Egison is focused on pattern matching of data. While OMeta is focused on pattern matching of syntax (so is used to create and extend new languages/DSLs). Is that a fair comparison?
How does the Egison online evaluator work? Server-side haskell or the ruby extension?
What you wrote is what I wanted to write.
We call the Egison command on the server limiting code with side-effects via an API server implemeted in Ruby.
All source code on Egison including its website is on GitHub.
Please check them, too.
https://github.com/egison
I’m not planning a javascript extension for now, though I’d like it.
Comments
Thanks. It looks to me like Egison is focused on pattern matching of data. While OMeta is focused on pattern matching of syntax (so is used to create and extend new languages/DSLs). Is that a fair comparison?
How does the Egison online evaluator work? Server-side haskell or the ruby extension?
Any plans for a javascript extension?
What you wrote is what I wanted to write. We call the Egison command on the server limiting code with side-effects via an API server implemeted in Ruby. All source code on Egison including its website is on GitHub. Please check them, too. https://github.com/egison I’m not planning a javascript extension for now, though I’d like it.