unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: Using a macro with FOLD alters FOLD procedure!
Date: Fri, 22 Apr 2005 08:16:26 +1000	[thread overview]
Message-ID: <878y3b93np.fsf@zip.com.au> (raw)
In-Reply-To: <426749AD.3090403@ossau.uklinux.net> (Neil Jerram's message of "Thu, 21 Apr 2005 07:35:25 +0100")

Neil Jerram <neil@ossau.uklinux.net> writes:
>
> We could certainly do this, but I think I remember a thread where it was 
> suggested that we treat any occurrence of a macro in non-car position as 
> an error - which would catch the problem more generally.

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?)


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


  reply	other threads:[~2005-04-21 22:16 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 [this message]
2005-04-22  8:27             ` Andy Wingo
2005-04-23 20:18             ` Neil Jerram

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=878y3b93np.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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).