unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: 白い熊 <guile-user_gnu.org@sumou.com>
To: guile-user@gnu.org
Subject: Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs
Date: Wed, 31 Jul 2013 08:47:25 +0400	[thread overview]
Message-ID: <a2b6597c-dc27-4b20-ba38-8da3c6f3fc12@email.android.com> (raw)
In-Reply-To: <1375237660.8252.42.camel@Renee-desktop.suse>

Nala Ginrut <nalaginrut@gmail.com> wrote:
>Here's a dilemma, unless guile/clisp/emacs have the same
>checker-procedure with same name and definition, you have no promise to
>check it under different language environment. The best way is
>prepossess which is portable.
Yes, I have been thinking very hard about this. The closest I came is apropos.

At least (apropos "guile") gives empty feedback in clisp and (apropos "clisp-data") is empty in guile and so on... So I could differentiate based on this.

However there's no numeric output so I can't do a cond based on (= ... comparison of output as= is the only equality function the three share so it seems back to square one.... So close....
--
白い熊



  reply	other threads:[~2013-07-31  4:47 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       ` 白い熊 [this message]
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

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=a2b6597c-dc27-4b20-ba38-8da3c6f3fc12@email.android.com \
    --to=guile-user_gnu.org@sumou.com \
    --cc=guile-user@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).