From: Jorge Javier Araya Navarro <jorgejavieran@yahoo.com.mx>
To: Eli Zaretskii <eliz@gnu.org>
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 15:29:38 -0600 [thread overview]
Message-ID: <8736gpfid9.fsf@yahoo.com.mx> (raw)
In-Reply-To: <83d0ftqyy4.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
El sábado 21 de septiembre del 2019 a las 1236 horas, Eli Zaretskii escribió:
>> From: Jorge Javier Araya Navarro <jorgejavieran@yahoo.com.mx>
>> Date: Sat, 21 Sep 2019 10:28:37 -0600
>>
>> 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.
>
> Are there any known problems with the ELisp implementation that
> justify reimplementing that in another language?
None to my knowledge. There is people and projects doing cool stuff like ecmascript[1] or
javascript_lexer[2] and I thought that leveraging from projects like those could provide any sort of
advantage to Emacs in speed, code maintenance or user experience.
I will try to present a dynamic module and see how that goes, after doing my due research on js.el
[1]: https://crates.io/crates/ecmascript
[2]: https://crates.io/crates/javascript_lexer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-09-21 21:29 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
2019-09-21 18:36 ` Eli Zaretskii
2019-09-21 21:29 ` Jorge Javier Araya Navarro [this message]
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=8736gpfid9.fsf@yahoo.com.mx \
--to=jorgejavieran@yahoo.com.mx \
--cc=eliz@gnu.org \
--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).