Skip to content
Lance Pollard edited this page Jun 11, 2014 · 17 revisions
  • build an incremental parser for super fast syntax highlighting and code completion.
  • land upon a common set of names for grammar rules (like punctuation.period and keyword.for, etc.).
  • describe workflow for creating a new language.
  • figure out ways patterns for translating between languages, so you could do things like compiling ruby to javascript or whatever you wanted.

Grammars to implement

Languages to implement, along with a rough guestimate on how difficult (or involved) they'd be, and whether or not it's started, or completed (percentage). Feel free to try and create one using the others as an example.

language difficulty status guides
clojure 1 open 1
lisp 1 open
json 1 open
csv 1 open
css 2 started
html 2 started
less 2 open
makefile 2 started
python 2 open
bash 3 started
javascript 4 open 1
r 4 open
ruby 4 open
c 5 open 1
dates 5 open 1
go 5 open
haskell 5 open
java 5 open
math 5 open 1
objective-c 5 open
rust 5 open
scala 5 started
sql 5 open
php ? open http://stackoverflow.com/questions/8931326/ebnf-grammar-definitions-for-php
assembly ? open https://github.com/sporst/Reverse-Engineering-Scripts/blob/master/antlr_x86/x86.g
http ? ? http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2.2
c# 10 ? http://msdn.microsoft.com/en-us/library/aa664812(v=vs.71).aspx

Transpilers

Clone this wiki locally