From: "Aurélien Aptel" <aurelien.aptel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Nicolas Goaziou <n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Rustom Mody <rustompmody-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
ragel-users-99ym4TKX+Hhg9hUCZPvPmw@public.gmane.org,
emacs-orgmode <emacs-orgmode-mXXj517/zsQ@public.gmane.org>
Subject: Re: GSoC 2012 -- Elisp backend for Ragel
Date: Tue, 27 Mar 2012 22:03:09 +0200 [thread overview]
Message-ID: <CA+5B0FP+ibOKuSfsfe2wpgNrA+eoWr-=JEoOTUSGoeGLdtoNBQ@mail.gmail.com> (raw)
In-Reply-To: <87vclsykl6.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Sun, Mar 25, 2012 at 1:40 PM, Nicolas Goaziou <n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> If so, I think it's ultimately a bad idea and it should be rewritten
>> using ragel.
>
> It may be. But it allows for flexibility. Org's syntax is evolving, and
> I consider org-element.el as a parser, but also as a guidance in that
> process. Since there is no formal description for Org syntax yet, an
> org-element.el is more useful than a full-blown parser generator for
> now.
Using a parser generator can be flexible too. Big changes in the
syntax usually implies big changes in the parsing code. With a tool
like ragel the operation is much less painful since the code is
generated. Also, if the org syntax can be written as a grammar, it can
be safely imported in other software that have a parser for it making
the format more portable.
> I don't know ragel (save for a short excursion in its website), but I'm
> pretty sure that even if it generates elisp code without dependency, any
> evolution to Org syntax will require to use it again. At that time, it
> may be difficult to find someone able and willing to undertake that
> updating task in a reasonable delay (since we're talking about a core
> feature). On the other hand, there are quite a few elisp hackers in
> Emacs's world.
Frankly, I don't know ragel very much either. I've only used it on
very simple things. But it's easy to use. You can even execute action
at any state while parsing a token (look closely at the example on the
homepage).
> Now, if ragel can improve org-element.el while preserving its
I'm not sure it's possible :/
> flexibility (and a compatible output, since I assume you won't also
> rewrite the generic export engine), I'm all ears.
Yes, the output of the parser has to remain the same otherwise I would
have to rewrite everything :p
next prev parent reply other threads:[~2012-03-27 20:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 13:43 GSoC 2012 -- Elisp backend for Ragel Rustom Mody
2012-03-23 11:12 ` Aurélien Aptel
2012-03-23 11:36 ` Rustom Mody
[not found] ` <CAJ+TeoebkVTLs9nrDTH_6xvzvkk1vTEZDL2iHmEAkTUfZRjpjQ@mail.gmail.com>
[not found] ` <CAJ+TeoebkVTLs9nrDTH_6xvzvkk1vTEZDL2iHmEAkTUfZRjpjQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-25 4:17 ` Rustom Mody
2012-03-25 6:55 ` Rustom Mody
2012-03-25 10:06 ` Aurélien Aptel
2012-03-25 11:40 ` Nicolas Goaziou
2012-03-25 12:52 ` Martyn Jago
2012-03-27 20:34 ` Aurélien Aptel
2012-03-27 21:22 ` Achim Gratz
2012-03-27 22:11 ` Aurélien Aptel
2012-03-28 6:34 ` Achim Gratz
2012-03-29 17:50 ` Aurélien Aptel
2012-03-29 17:52 ` Samuel Wales
2012-03-29 19:04 ` Achim Gratz
[not found] ` <87vclsykl6.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-03-27 20:03 ` Aurélien Aptel [this message]
2012-03-26 16:01 ` Bastien
[not found] ` <87wr674aii.fsf-mXXj517/zsQ@public.gmane.org>
2012-03-27 20:49 ` Aurélien Aptel
2012-03-27 22:10 ` Bastien
2012-03-26 15:53 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2012-03-21 18:51 Aurélien Aptel
2012-03-21 19:32 ` Aurélien Aptel
2012-03-21 19:34 ` Samuel Wales
2012-03-22 12:22 ` Thorsten
2012-03-24 8:16 ` Nicolas Goaziou
2012-03-26 16:03 ` Bastien
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+5B0FP+ibOKuSfsfe2wpgNrA+eoWr-=JEoOTUSGoeGLdtoNBQ@mail.gmail.com' \
--to=aurelien.aptel-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
--cc=n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=ragel-users-99ym4TKX+Hhg9hUCZPvPmw@public.gmane.org \
--cc=rustompmody-Re5JQEeQqe8AvxtiuMwx3w@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).