From: Ergus <spacibba@aol.com>
To: Jorge Javier Araya Navarro <jorgejavieran@yahoo.com.mx>
Cc: emacs-devel@gnu.org
Subject: Re: are contributions on other programming languages than C and Emacs lisp bad idea?
Date: Sat, 21 Sep 2019 19:22:04 +0200 [thread overview]
Message-ID: <20190921172204.uymwzzotpf4fsfx4@Ergus> (raw)
In-Reply-To: <874l15fway.fsf@yahoo.com.mx>
On Sat, Sep 21, 2019 at 10:28:37AM -0600, Jorge Javier Araya Navarro wrote:
>
>
>El s?bado 21 de septiembre del 2019 a las 0346 horas, Stephen Leake escribi?:
>
>> There is an example currently in ELPA; the wisi package provides a
>> parser generator written in Ada, and an elisp interface that runs the
>> generated executable in an external process. The ada-mode and
>> wisitoken-grammar-mode packages use wisi.
>>
>> This requires an Ada compiler to fully install the packages.
>>
>> So far, this is all focussed on ada-mode; users of that mode are very
>> likely to have a native Ada compiler installed, so there's no extra
>> burden. But if other modes are implemented using wisi, it could become
>> one. On the other hand, gcc provides an Ada compiler, so it's not a
>> big burden.
>
>I'm actually looking to do something like this but for JavaScript, there are several packages in
>Rust that can help parsing JavaScript code and I thought this could become handy and replace the
>existing parsing written in Emacs Lisp.
While I am find with the consideration of adding new languages to
develop/extend emacs... I am pretty sure there should be also some
projects to parse javascript in C... We only need to contact the authors
of the projects to ask them about their position to use their
code...
For emacs with rust there is an interesting project under developement:
https://github.com/remacs/remacs
That maybe is the future ;) who knows...
next prev parent reply other threads:[~2019-09-21 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1427040605.4453251.1569007946448.ref@mail.yahoo.com>
2019-09-20 19:32 ` are contributions on other programming languages than C and Emacs lisp bad idea? Jorge Araya Navarro
2019-09-20 21:11 ` Paul Eggert
2019-09-20 22:34 ` Stefan Monnier
2019-09-21 0:37 ` Jorge Javier Araya Navarro
2019-09-21 2:52 ` Devesh Sukhwal
2019-09-21 13:09 ` Stefan Monnier
2019-09-21 9:03 ` VanL
2019-09-21 9:46 ` Stephen Leake
2019-09-21 16:28 ` Jorge Javier Araya Navarro
2019-09-21 17:22 ` Ergus [this message]
2019-09-21 18:36 ` Eli Zaretskii
2019-09-21 21:29 ` Jorge Javier Araya Navarro
2019-09-22 15:01 ` Eli Zaretskii
2019-09-22 19:01 ` yyoncho
2019-09-22 3:51 ` Richard Stallman
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=20190921172204.uymwzzotpf4fsfx4@Ergus \
--to=spacibba@aol.com \
--cc=emacs-devel@gnu.org \
--cc=jorgejavieran@yahoo.com.mx \
/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).