From: Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de>
Cc: guile-devel@gnu.org
Subject: Re: define and modules
Date: Wed, 6 Nov 2002 18:20:13 +0100 (CET) [thread overview]
Message-ID: <Pine.GSO.4.05.10211061813540.16088-100000@sallust.ida.ing.tu-bs.de> (raw)
In-Reply-To: <0211060216541H.07034@locke.free-expression.org>
On Wed, 6 Nov 2002, Lynn Winebarger wrote:
> On Wednesday 06 November 2002 01:54, Dirk Herrmann wrote:
> > On 4 Nov 2002, Marius Vollmer wrote:
> >
> > > Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de> writes:
> > >
> > > > OK, talking about the right thing: How should guile react to the
> > > > following code:
> > > >
> > > > (define define-private define)
> > > >
> > > > This is done in boot9.scm. Should this be allowed?
> > >
> > > No, since 'define' is a syntactic keyword... which is probably not the
> > > reason you were expecting, right?
> >
> > It is exactly the reason. The question is, how should guile react here?
>
> "Syntax error: invalid use of define" or "Syntax error: invalid define form"?
I think this is not general enough. It works for the special case of
define, but the point is not, that the define form is broken, but that a
macro is used as an argument to something else. Consider
(call-foo define)
The point that we have to decide is, whether such a form is reported as a
syntax error during memoization, or whether we just don't dereference the
macro during memoization and let the executor do the lookup. The second
choice will allow that a new definition of the macro may be provided in
the meantime. For example:
(define (foo) (call-foo and))
(define and #t)
(foo)
Should this be possible? If so, then can't signal an error
_during_memoization_ if a macro is used at some illegal place.
Best regards,
Dirk
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-11-06 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-20 16:17 define and modules Dirk Herrmann
2002-11-03 16:25 ` Marius Vollmer
2002-11-04 21:32 ` Dirk Herrmann
2002-11-04 22:12 ` Marius Vollmer
2002-11-06 6:54 ` Dirk Herrmann
2002-11-06 7:16 ` Lynn Winebarger
2002-11-06 17:20 ` Dirk Herrmann [this message]
2002-11-06 17:51 ` Lynn Winebarger
2002-11-06 22:27 ` Dirk Herrmann
2002-11-17 20:30 ` Marius Vollmer
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=Pine.GSO.4.05.10211061813540.16088-100000@sallust.ida.ing.tu-bs.de \
--to=dirk@sallust.ida.ing.tu-bs.de \
--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).