3 ms·
Is it really useful to write a formal spec for Github Markdown? The software they use to parse and render it is open source. If you want to know how exactly som
by adrianN 10y ago
Is it really useful to write a formal spec for Github Markdown? The software they use to parse and render it is open source. If you want to know how exactly something works, you can read the source.
- scrollaway 10y agoIs it really useful to write a formal spec for HTML? The software we use to parse and render it is open source. If you want to know how exactly something works, you can read the source. ;)
- UK-AL 10y agoReading the sources and trying to understand it takes a lot longer than looking at bnf and cranking out recursive descent parser based on it or a parser generator.
- dreamcompiler 10y agoIt's not possible to write a BNF for Markdown. At least not an unambiguous, useful BNF. http://roopc.net/posts/2014/markdown-cfg/ http://roopc.net/posts/2014/markdown-cfg/
- legulere 10y agoYes, if you also want to have more implementations, that can differ in e.g. license or programming language. For instance it is the reason why there's no reimplementation of TeX.
- adrianN 10y agoThere is pdflatex, luatex,... Nobody stops you from translating the Ruby or whatever into your favorite language.
- jws 10y agoHaving used and maintained a Swift translation of the StackOverflow .NET markdown processor, please, when there is a proposal to use source as a spec, burn it with fire. Scatter the ashes.