unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Jorge Araya Navarro <jorgejavieran@yahoo.com.mx>
Cc: Emacs Developers <emacs-devel@gnu.org>
Subject: Re: are contributions on other programming languages than C and Emacs lisp bad idea?
Date: Fri, 20 Sep 2019 14:11:30 -0700	[thread overview]
Message-ID: <94c124f9-a903-ef4a-42cb-6a28e29028b3@cs.ucla.edu> (raw)
In-Reply-To: <1427040605.4453251.1569007946448@mail.yahoo.com>

Modules can be written in any language that can grok a C API. The GNU Coding 
Standards suggest using C for Emacs core, and I expect we'd need a pretty good 
reason to depart from that. Despite inroads from other languages C is still 
kinda the lingua franca for low level stuff.



  reply	other threads:[~2019-09-20 21:11 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 [this message]
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
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=94c124f9-a903-ef4a-42cb-6a28e29028b3@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --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).