From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Cc: clisp-devel@lists.sourceforge.net
Subject: Re: A Modest Proposal
Date: Thu, 14 Apr 2011 18:56:12 +0200 [thread overview]
Message-ID: <87lizcbwlv.fsf@gnu.org> (raw)
In-Reply-To: BANLkTimyVq6ceY9HxN8zVFGJuo5CK5eBmg@mail.gmail.com
Hi,
William ML Leslie <william.leslie.ttg@gmail.com> writes:
> 0. Objects in javascript are maps from string keys to any value. If
> they are to be cast as hashes or dictionaries when passed to a
> language that allows non-string keys, and the language adds a
> non-string key, what happens to the javascript object?
For a simpler example, see Elisp’s #nil in Guile. The question of how
Scheme code should handle it wasn’t an easy one...
Thanks,
Ludo’.
next prev parent reply other threads:[~2011-04-14 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 13:45 A Modest Proposal Noah Lavine
2011-04-13 15:23 ` Pascal J. Bourguignon
2011-04-14 1:35 ` Noah Lavine
2011-04-14 2:06 ` William ML Leslie
2011-04-14 16:56 ` Ludovic Courtès [this message]
2011-04-16 20:46 ` Noah Lavine
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=87lizcbwlv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=clisp-devel@lists.sourceforge.net \
--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).