Crossposting: question about non-CFG parsing. The Haskell ecosystem may have an answer, and I wouldn't mind using Haskell for this.

• pandoc

  420 32,312 9.8 Haskell

  Universal markup converter

My concern about that is that I feel the Pandoc AST is designed for Markdown, and I think AsciiDoc is significantly more complex. Also, Pandoc doesn't do annotated ASTs with source position information, which I want ( https://github.com/jgm/pandoc/issues/4565 ).

• asciidoc-hs

  1 44 0.0 Haskell

  AsciiDoc parser that can be used as a Pandoc front-end, written in Haskell

My grammar for inlines solves what I think is the most difficult part of the language: the mutual nesting of constrained/unconstrained inline styling. It has been very well received by the AsciiDoc standardization WG, as a good sign that the task of formally defining the language is feasible. This is not to say that there's not a lot of work ahead to complete both inline and block description, including challenging parts as escape sequences, and that even this part of the grammar is not going to be changed a lot in the future.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project