From: Thien-Thi Nguyen <ttn@gnu.org>
To: 白い熊 <guile-user_gnu.org@sumou.com>
Cc: guile-user@gnu.org
Subject: Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs
Date: Mon, 12 Aug 2013 14:48:31 +0200 [thread overview]
Message-ID: <87eh9zt6qo.fsf@zigzag.favinet> (raw)
In-Reply-To: <c6c357f23e0e9d02bef7410fdb5b66fa@hcoop.net> ("白い熊"'s message of "Thu, 01 Aug 2013 16:42:31 +0400")
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
() 白い熊 <guile-user_gnu.org@sumou.com>
() Thu, 01 Aug 2013 16:42:31 +0400
So if anyone would have alternate ideas [...]
If you are comfortable w/ starting from a Lisp (Emacs or CLISP) base,
perhaps you can find fruitful the "recode" facility of CEDET:
http://www.emacswiki.org/emacs/SemanticRecoder
This addresses the (unavoidable, you will see) translation requirement,
not the "distinguishing the fragility of superficial syntax similarity"
part (avoidable, but nonetheless fun to experiment with :-D). Anyway,
you can see what pains CEDET takes to grow text into a (com)pliant tree.
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2013-08-12 12:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 8:21 Determining programatically whether the interpreter is Guile or Clisp or Emcs 白い熊
2013-07-29 8:36 ` Nala Ginrut
2013-07-29 11:21 ` 白い熊
2013-07-29 11:32 ` Nala Ginrut
2013-07-29 11:53 ` 白い熊
2013-07-31 2:27 ` Nala Ginrut
2013-07-31 4:47 ` 白い熊
2013-07-31 5:35 ` Nala Ginrut
2013-07-31 5:35 ` Nala Ginrut
2013-07-31 6:28 ` 白い熊
2013-07-31 6:48 ` Nala Ginrut
2013-09-07 9:31 ` Andy Wingo
2013-07-31 10:24 ` Alexei Matveev
2013-07-31 10:20 ` Ralf Mattes
2013-08-01 1:12 ` Nala Ginrut
2013-08-01 12:42 ` 白い熊
2013-08-01 12:45 ` 白い熊
2013-08-12 12:48 ` Thien-Thi Nguyen [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eh9zt6qo.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=guile-user@gnu.org \
--cc=guile-user_gnu.org@sumou.com \
/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).