From: mb21 <mauro.bieg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: BNF presentation of Pandoc AST, anybody?
Date: Fri, 30 Apr 2021 00:23:56 -0700 (PDT) [thread overview]
Message-ID: <d7407dfb-c6ee-42b7-a4cd-b1500b228962n@googlegroups.com> (raw)
In-Reply-To: <3F6BC311-C472-4F2E-8092-4FB10D50A279-ee4meeAH724@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1730 bytes --]
Text.Pandoc.Definition.Pandoc is written in Haskell syntax, so arguably
that's already BNF-like..? Which appraoch/tool to use really depends on
what you want to do with the tree after that..
On Sunday, April 25, 2021 at 8:19:59 PM UTC+2 ros...-ee4meeAH724@public.gmane.org wrote:
> Does anybody have a BNF-style grammar that presents
> the AST structure of Text.Pandoc.Definition.Pandoc?
>
> Something generally like:
>
> Pandoc = Meta (Block)*
> Meta = (Text → MetaValue)*
> MetaValue = MetaMap | MetaList | MetaBool | MetaString | MetaInlines
> |MetaBlocks
> MetaMap = (Text → MetaValue)*
> MetaList = (MetaValue)*
> MetaBool = Bool
> MetaString = Text
> MetaInlines = (Inline)*
> MetaBlocks = (Block)*
> Block = …
>
> and so on. Each producti0n is a data constructor application.
> Basic stuff like Map and List would get their own BNF-style
> syntax.
>
> Or maybe a railway graph? I started to make a cheat-sheet,
> but surely such a thing has already been done.
>
> TIA,
> — John
>
> P.S. Also, someone has surely written an interpreter,
> maybe a framework, that starts something like this:
>
> ```{.lua-exec #thatOne}
> return 42
> ```
> neutral content
> ```{.lua-exec #thisOne}
> print(thatOne)
> ```
>
> Any hints on where such a thing might be?
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/d7407dfb-c6ee-42b7-a4cd-b1500b228962n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2298 bytes --]
prev parent reply other threads:[~2021-04-30 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 18:19 'John Rose' via pandoc-discuss
[not found] ` <3F6BC311-C472-4F2E-8092-4FB10D50A279-ee4meeAH724@public.gmane.org>
2021-04-30 7:23 ` mb21 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d7407dfb-c6ee-42b7-a4cd-b1500b228962n@googlegroups.com \
--to=mauro.bieg-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).