From: Tom <adatgyujto@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Adding c/c++ scripting
Date: Sat, 23 Jan 2016 08:33:04 +0000 (UTC) [thread overview]
Message-ID: <loom.20160123T093054-984@post.gmane.org> (raw)
In-Reply-To: BY1PR18MB003907198A2AF56DE6A2BA6B83C50@BY1PR18MB0039.namprd18.prod.outlook.com
jonathan maharaj <unidef_rogue <at> live.com> writes:
>
>
> Instead of scheme for emacs I'd like it to support c/c++ or any language
>
There are attempts to use other languages. For example, this fairly new
project uses the Python tokenizer to emit emacs vm bytecode:
https://github.com/vkazanov/elang
next prev parent reply other threads:[~2016-01-23 8:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 4:20 Adding c/c++ scripting jonathan maharaj
2016-01-23 8:33 ` Tom [this message]
2016-01-24 1:54 ` Richard Stallman
2016-01-26 17:38 ` John Wiegley
2016-01-24 1:23 ` Xue Fuqiao
2016-01-24 5:35 ` Tom
2016-01-25 8:46 ` Xue Fuqiao
2016-01-26 17:59 ` Vibhav Pant
2016-01-25 1:44 ` 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=loom.20160123T093054-984@post.gmane.org \
--to=adatgyujto@gmail.com \
--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).