From: <dsmich@roadrunner.com>
To: Bill Schottstaedt <bil@ccrma.Stanford.EDU>, bug-guile@gnu.org
Subject: Re: quote oddity
Date: Fri, 1 Apr 2011 18:29:25 -0400 [thread overview]
Message-ID: <20110401222925.RGC7T.52485.root@cdptpa-web26-z01> (raw)
In-Reply-To: <20110401213750.M91783@ccrma.Stanford.EDU>
---- Bill Schottstaedt <bil@ccrma.Stanford.EDU> wrote:
> Does this strike you guys as kind of odd?
>
> guile> ((lambda (s c) (s c)) quote #f)
> c
> guile> ((lambda (q) (let ((x 1)) (q x))) quote)
> x
>
> I can't decide what I think.
Well, quote is syntax. You can't pass it around like a function. Guile 2.0 fixes that:
scheme@(guile-user)> ((lambda (s c) (s c)) quote #f)
While compiling expression:
ERROR: Syntax error:
unknown location: quote: bad syntax in form quote
scheme@(guile-user)> ((lambda (q) (let ((x 1)) (q x))) quote)
While compiling expression:
ERROR: Syntax error:
unknown location: quote: bad syntax in form quote
-Dale
next prev parent reply other threads:[~2011-04-01 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 21:38 quote oddity Bill Schottstaedt
2011-04-01 22:29 ` dsmich [this message]
2011-04-01 22:53 ` Bill Schottstaedt
2011-04-02 0:19 ` Andy Wingo
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=20110401222925.RGC7T.52485.root@cdptpa-web26-z01 \
--to=dsmich@roadrunner.com \
--cc=bil@ccrma.Stanford.EDU \
--cc=bug-guile@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).