unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Richard M Stallman <rms@gnu.org>
To: Clinton Ebadi <clinton@unknownlamer.org>
Cc: d@domob.eu, guile-devel@gnu.org, emacs-devel@gnu.org
Subject: Re: GSoC: Emacs  Lisp support for GNU Guile
Date: Sat, 04 Apr 2009 18:00:08 -0400	[thread overview]
Message-ID: <E1LqDuK-0000wH-9F@fencepost.gnu.org> (raw)
In-Reply-To: <87skktqvwg.fsf@unknownlamer.org> (message from Clinton Ebadi on Tue, 31 Mar 2009 16:28:47 -0400)

     - Remove handling of NIL in Scheme. This special casing is, in my
       opinion, distressingly unclean. This would require adding a new
       ELISP-IF form that accepts #f/nil as false values

We carefully designed ways to handle nil, #f and () in Guile
so as to be able to intermix Lisp and Scheme programs.
That was 14 years ago, and I don't recall what we decided.  But I think
the idea was that #f and () would be eq when viewed
from Lisp, but not eq when viewed from Scheme.

I don't know whether this design was actually implemented.

We should not make changes in this based on a rigid idea that
something is "unclean".  To make the two languages interoperate
properly on the same data requires careful design, and it's
possible that something less than totally elegant is the only
way to make it work at all.






  parent reply	other threads:[~2009-04-04 22:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 19:44 GSoC: Emacs Lisp support for GNU Guile Daniel Kraft
2009-03-31 20:28 ` Clinton Ebadi
2009-03-31 22:34   ` Neil Jerram
2009-03-31 23:10   ` Andy Wingo
2009-04-04 22:00   ` Richard M Stallman [this message]
2009-03-31 22:23 ` Neil Jerram
2009-03-31 23:15   ` Andy Wingo
2009-04-01  2:30     ` Mike Gran
2009-03-31 23:05 ` Andy Wingo
2009-03-31 23:41   ` Neil Jerram
2009-04-01 15:36   ` Daniel Kraft
2009-04-01 13:31 ` Stefan Monnier
2009-04-03 17:30   ` Andy Wingo
2009-04-03 20:31     ` Chong Yidong
2009-04-03 23:50       ` Andy Wingo
2009-04-06 23:26       ` Samuel Bronson
2009-04-07  0:52         ` Stefan Monnier
2009-04-05 10:11     ` Ludovic Courtès

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=E1LqDuK-0000wH-9F@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=clinton@unknownlamer.org \
    --cc=d@domob.eu \
    --cc=emacs-devel@gnu.org \
    --cc=guile-devel@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).