From: Po Lu <luangruo@yahoo.com>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel@gnu.org, Theodor Thornhill <theo@thornhill.no>
Subject: Re: tree-sitter and Android port
Date: Tue, 21 Feb 2023 13:33:20 +0800 [thread overview]
Message-ID: <87edqjeg67.fsf@yahoo.com> (raw)
In-Reply-To: <0079408F-76B4-4BEF-A473-C3EF2E98B5CE@gmail.com> (Yuan Fu's message of "Mon, 20 Feb 2023 18:56:40 -0800")
Yuan Fu <casouri@gmail.com> writes:
> I’ve looked at this before. The “uncompiled grammar file”, grammar.c,
> not only contains static data, but also functions. Some language also
> requires a scanner.cc <http://scanner.cc/> file which contains
> nontrivial functions. So to “interpret” the grammar file you
> essentially need a C (and sometimes even C++) compiler.
Is there any chance of this situation changing?
In the future, we will see more and more systems where these kinds of
restrictions are common, so it would be a good idea for a solution to be
found. Thanks.
next prev parent reply other threads:[~2023-02-21 5:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ttzkmrw1.fsf.ref@yahoo.com>
2023-02-17 11:51 ` Android port Po Lu
2023-02-17 12:26 ` Eric S Fraga
2023-02-17 12:56 ` Arsen Arsenović
2023-02-17 13:05 ` Po Lu
2023-02-17 13:21 ` Arsen Arsenović
2023-02-19 11:17 ` Arsen Arsenović
2023-02-19 12:21 ` Po Lu
2023-02-19 14:16 ` Po Lu
2023-02-19 14:40 ` Arsen Arsenović
2023-02-19 15:13 ` Arsen Arsenović
2023-02-20 2:37 ` Po Lu
2023-02-20 15:33 ` Arsen Arsenović
2023-02-20 15:46 ` Po Lu
2023-02-20 16:05 ` Arsen Arsenović
2023-02-19 14:42 ` Arsen Arsenović
2023-02-17 13:50 ` tomas
2023-02-20 14:23 ` tree-sitter and " Po Lu
2023-02-20 15:38 ` Arsen Arsenović
2023-02-21 2:27 ` Po Lu
2023-02-21 2:56 ` Yuan Fu
2023-02-21 5:33 ` Po Lu [this message]
2023-02-21 13:41 ` Po Lu
2023-03-10 20:07 ` Etienne Prud'homme
2023-03-10 23:50 ` Po Lu
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=87edqjeg67.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=theo@thornhill.no \
/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).