4 ms·
If you're interested in stuff like this, be sure to also check out Rascal: http://www.rascal-mpl.org http://www.rascal-mpl.org The focus is slightly different
by skrebbel 12y ago
If you're interested in stuff like this, be sure to also check out Rascal:
http://www.rascal-mpl.org http://www.rascal-mpl.org
The focus is slightly different: Rascal focuses more on automated code transformations and less on being a syntax highlighting service for editors. But Rascal is remarkably powerful and surprisingly accessible.
Basically, Rascal allows you to build Lispy macros in any language. Or to easily parse-and-transform new languages. Or to design entirely new languages and transpile them into something existing. To drive the point home, CoffeeScript, Nimrod and Sass could've easily been built with Rascal.
- CmonDev 12y ago"being a syntax highlighting service for editors" - a bit of an understatement for syntax checking and future refactoring capabilities.
- skrebbel 12y agoI'm not sure that listing all the features Nitra has and Rascal doesn't (or the other way around) is going to help make my point, so you're going to have to do with just one.
- Araq 12y agoAs the primary author of Nimrod I disagree. ;-) And to be blunt: I know the person has no idea of what he talks about when he uses the word "transpile".
- skrebbel 12y agoHa! Honoured to have you reply to my comment, sir :-) I wonder, what is the primary reason you believe a tool like Rascal couldn't be the engine behind the Nimrod compiler? (btw, I didn't mean to imply that making the Nimrod compiler is easy in any language - I guess the "easy" word applies more to CoffeeScript and Sass in my previous comment) Regarding the word "transpile" - that was long the common name given to e.g. the CoffeeScript compiler and only recently got out of fashion for obvious reasons. Mind that not everyone who uses an outdated term is entirely clueless. :-)