unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Helmut Eller <eller.helmut@gmail.com>
To: Danny McClanahan <dmcc2@hypnicjerk.ai>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: rosie/libpexl library for regex pattern composition
Date: Sun, 28 Jul 2024 09:08:06 +0200	[thread overview]
Message-ID: <8734nudmeh.fsf@gmail.com> (raw)
In-Reply-To: <disFmiXATNq6Fywm_Y7OS4MzSw81H4xm0k1UQ_aAvvC2GsXEAYUXa94WCtJI5TMMhjXnyI_89vovpGAHB-G-kg1WA2-wssPGokj8LWpdAgo=@hypnicjerk.ai> (Danny McClanahan's message of "Sat, 27 Jul 2024 13:04:28 +0000")

On Sat, Jul 27 2024, Danny McClanahan wrote:

> Rosie/PEXL's goals are explicitly focused more on maintainability than
> sheer performance, so I'm thinking it might make sense to introduce
> Rosie as a separate interface to the regex engine, while we can keep
> the regex engine narrowly focused on patterns that we can more easily
> optimize.

AFAIU, Rosie is based on parsing expression grammars, i.e. it's not a
regular language and it's in a different complexity class.

I think it would be best for Emacs to provide an efficient C API for
dynamic modules to buffer text with the explicit goal to support
alternative regexp engines and parsing libraries.

It seems that tree-sitter only needs a single function:
treesit_read_buffer.  If it works for tree-sitter, then maybe it's also
good enough for Rosie.

Helmut



  reply	other threads:[~2024-07-28  7:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-27 13:04 rosie/libpexl library for regex pattern composition Danny McClanahan
2024-07-28  7:08 ` Helmut Eller [this message]
2024-07-28  7:51   ` Eli Zaretskii
2024-07-29 13:58     ` Danny McClanahan
2024-07-29 19:33       ` Helmut Eller

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8734nudmeh.fsf@gmail.com \
    --to=eller.helmut@gmail.com \
    --cc=dmcc2@hypnicjerk.ai \
    --cc=emacs-devel@gnu.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.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).