3 ms·

> There's no compatibility issue That's not really true, is it though? Scheme '(), #f and so forth...

• tedks 12y ago
  As I said in my comment, >Guile can run elisp already Guile already interprets Elisp. Elisp can run unmodified on Guile. Guile, the virtual machine, contains a front-end for Emacs Lisp. المكر ينفذ أصلا إيماكس اللثغة. Guile jatorriz exekutatzen emacs Lisp. It is true there are no compatibility issues because Guile is an implementation of Emacs Lisp.
  • wtbob 12y ago
    From the same thread https://lists.gnu.org/archive/html/emacs-devel/2014-09/msg00500.html https://lists.gnu.org/archive/html/emacs-devel/2014-09/msg00... > It's not a 100% drop-in replacement, that's true…(eq foo t) should always work. (eq foo nil) will only work if that `nil' came from Elisp code; if it's a Scheme #f or '() in disguise, then you need to make that (not foo) or (null foo) (both works in both cases); anything but (eq foo nil).
    • tedks 12y ago
      That seems to imply that the problem is in the Scheme/Elisp interface, not in Guile's execution of pure Elisp.
    • taylanub 12y ago
      Note that using the `not' and `null' functions instead of comparing equality to `nil' is good coding style anyway.