unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org
Subject: Re: Using a macro with FOLD alters FOLD procedure!
Date: Sat, 23 Apr 2005 21:18:33 +0100	[thread overview]
Message-ID: <426AAD99.2080700@ossau.uklinux.net> (raw)
In-Reply-To: <878y3b93np.fsf@zip.com.au>

Kevin Ryde wrote:
> I suppose it depends if a macro should be a first class object to be
> thrown around (or do I misunderstand?).
> 
> I've been gradually converting srfi-1 procs to C, which has the side
> effect of checking the procs are actual procedures.  I suppose there
> must be plenty of ordinary application code passing procedures around
> in exactly the same way that's vulnerable to memoizing macros.
> 
> (Could a memoized form check it's got the same macro as originally
> expanded, as a safety check?  Or do I misunderstand again?)
> 

I think you understand fine - to the extent that I understand myself, 
anyway.

For reference, here's the first message in the 2002 thread that I 
mentioned: 
http://lists.gnu.org/archive/html/guile-devel/2002-01/msg00030.html

The key mail in this thread is probably Marius's one.  I have to say, 
though, that I don't yet understand how Marius's solution would solve 
the problem in the case of passing a macro to fold.

Regards,
	Neil



_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


      parent reply	other threads:[~2005-04-23 20:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-15 18:38 Using a macro with FOLD alters FOLD procedure! Steve Juranich
2005-04-15 19:50 ` Stephen Compall
2005-04-15 22:20   ` Steve Juranich
2005-04-16 11:46     ` Neil Jerram
2005-04-18  0:45       ` Rob Browning
2005-04-21  6:35         ` Neil Jerram
2005-04-21 22:16           ` Kevin Ryde
2005-04-22  8:27             ` Andy Wingo
2005-04-23 20:18             ` Neil Jerram [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=426AAD99.2080700@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-user@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).