[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Determining programatically whether the interpreter is Guile or Clis
From: |
白い熊 |
Subject: |
Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs |
Date: |
Wed, 31 Jul 2013 08:47:25 +0400 |
User-agent: |
K-9 Mail for Android |
Nala Ginrut <address@hidden> 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....
--
白い熊
- Determining programatically whether the interpreter is Guile or Clisp or Emcs, 白い熊, 2013/07/29
- Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs, Nala Ginrut, 2013/07/29
- Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs, 白い熊, 2013/07/29
- Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs, Nala Ginrut, 2013/07/30
- Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs,
白い熊 <=
- Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs, Nala Ginrut, 2013/07/31
- Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs, Nala Ginrut, 2013/07/31
- Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs, 白い熊, 2013/07/31
- Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs, Nala Ginrut, 2013/07/31
Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs, Alexei Matveev, 2013/07/31