From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: TXR Lisp vs elisp.
Date: Wed, 1 Sep 2021 20:20:17 +0800 [thread overview]
Message-ID: <CAGP6POJ4R0BT9VzOWCfU88tmRyZvFYFHsCSu7Z6Qg17R+oHfEQ@mail.gmail.com> (raw)
In-Reply-To: <CAGP6PO+4WS+qZCB2H3K2F8roa8=rVqUSFrhGWrALAO_VJ7bHMA@mail.gmail.com>
On Wed, Sep 1, 2021 at 1:37 PM Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
>
> I noticed the TXR Lisp from here [1]. Does anyone here have
> experiences on this lisp dialect?
>
> [1] http://nongnu.org/txr/txr-lisp.html
Based on the following description on its official website [2], this
language seems superior:
The other language in TXR is TXR Lisp. This is not an implementation
of an existing Common Lisp or Scheme, but a new dialect, which
contains many new ideas. TXR Lisp is feature-rich, and oriented toward
succinct, convenient expressivity. While staying completely true to
the Lisp heritage, it takes cues from new scripting and functional
languages.
TXR Lisp programs are shorter and clearer than those written in some
mainstream languages "du jour" like Python, Ruby, Clojure, Javascript
or Racket. If you find that this isn't the case, the TXR project wants
to hear from you; give a shout to the mailing list. If a program is
significantly clearer and shorter in another language, that is
considered a bug in TXR.
[2] http://nongnu.org/txr/index.html
Best, Hongyi
next prev parent reply other threads:[~2021-09-01 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 5:37 TXR Lisp vs elisp Hongyi Zhao
2021-09-01 12:20 ` Hongyi Zhao [this message]
2021-09-03 3:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-03 3:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-03 17:01 ` [External] : " Drew Adams
2021-09-04 10:56 ` Wayne Harris via Users list for the GNU Emacs text editor
2021-09-04 13:46 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-04 13:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-04 15:11 ` Wayne Harris via Users list for the GNU Emacs text editor
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=CAGP6POJ4R0BT9VzOWCfU88tmRyZvFYFHsCSu7Z6Qg17R+oHfEQ@mail.gmail.com \
--to=hongyi.zhao@gmail.com \
--cc=help-gnu-emacs@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.
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).