unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: "Bill Schottstaedt" <bil@ccrma.Stanford.EDU>
Cc: bug-guile@gnu.org
Subject: Re: quote oddity
Date: Sat, 02 Apr 2011 02:19:24 +0200	[thread overview]
Message-ID: <m3zko9tshf.fsf@unquote.localdomain> (raw)
In-Reply-To: <20110401224911.M70351@ccrma.Stanford.EDU> (Bill Schottstaedt's message of "Fri, 1 Apr 2011 15:53:10 -0700")

On Sat 02 Apr 2011 00:53, "Bill Schottstaedt" <bil@ccrma.Stanford.EDU> writes:

>> Well, quote is syntax.  You can't pass it around like a function.  Guile 2.0 fixes that: 
>
> that's an improvement?  

I *think* so.  I think we can agree that in general uniformity is
better, and this case certainly has that property.

I don't know how supporting first-class syntax could help anything in
this case.

Andy
-- 
http://wingolog.org/



      reply	other threads:[~2011-04-02  0:19 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
2011-04-01 22:53   ` Bill Schottstaedt
2011-04-02  0:19     ` Andy Wingo [this message]

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=m3zko9tshf.fsf@unquote.localdomain \
    --to=wingo@pobox.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).