From: "Dhruva Krishnamurthy" <dhruvakm@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: emacs rewrite
Date: Sun, 2 Apr 2006 16:38:09 +0530 [thread overview]
Message-ID: <e3f230850604020408k3d99c9efkc9fdb7528f0aabc8@mail.gmail.com> (raw)
In-Reply-To: <E1FPn5y-0003Kn-Gr@lists.gnu.org>
Hello,
Not sure how serious the emacs development folks are about this.
IMHO, we should be using C++ and PYTHON. Though I prefer structured C
programs, for projects of GNU Emacs scale, it makes it easier to use
an object oriented language like C++. From the little knowledge I have
on PYTHON, I am suggesting it as it is object oriented and is a
functional programing language too. Another tool worth exploring be it
PERL/PYTHON is SWIG (Simplified Wrapper Interface Generator) with
which C/C++ APIs can exposed to PERL/PYTHON (other languages
supported).
IMO, the language of choice for present times must be driven by the
levels of abstraction it supports so that development is easier
without everyone having to understand the guts of the core
implementation.
If there is enough steam, I would love to get involved in any way I
can be of help, please take this forward.
with warm regards,
dhruva
On 4/2/06, Richard Stallman <rms@gnu.org> wrote:
>
> After more than 30 years I think it's time to rewrite emacs from scratch.
>
> I would be happy to hear your suggestions about the best language to use.
>
> At the moment I think that Perl would be the best fit, because of its acronym:
>
> Perfect emacs rewriting language.
>
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel
>
--
Dhruva Krishnamurthy
GNU/FSF member: 1935
next prev parent reply other threads:[~2006-04-02 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-01 20:53 emacs rewrite Richard Stallman
2006-04-01 21:51 ` Frank Schmitt
2006-04-01 22:18 ` Jay Belanger
2006-04-03 1:08 ` Richard Stallman
2006-04-03 13:00 ` Stephen J. Turnbull
2006-04-03 22:10 ` Bill Wohler
2006-04-04 13:52 ` Richard Stallman
2006-04-02 6:01 ` Ramprasad B
2006-04-02 11:08 ` Dhruva Krishnamurthy [this message]
2006-04-02 22:34 ` Bill Wohler
2006-04-03 7:20 ` Thien-Thi Nguyen
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=e3f230850604020408k3d99c9efkc9fdb7528f0aabc8@mail.gmail.com \
--to=dhruvakm@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).