unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Problems with LOAD and latest build
Date: Thu, 03 Sep 2009 10:43:39 +0200	[thread overview]
Message-ID: <m34ork2zb8.fsf@pobox.com> (raw)
In-Reply-To: <874oro74lh.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 31 Aug 2009 10:46:50 +0200")

On Mon 31 Aug 2009 10:46, ludo@gnu.org (Ludovic Courtès) writes:

> Hi,
>
> Andy Wingo <wingo@pobox.com> writes:
>
>> Now, does this indicate a bug in Guile, or at least an undesirable
>> behavior?
>
> Yes, I think so.
>
> Programs that want to rely on bare R5RS (e.g., SILex) have nothing else
> but `load' to have code in separate files.  So I think the compiler
> should special-case top-level `load', `primitive-load', etc., calls.

Programs that rely on bare R5RS still need some help in Guile 1.8 to
load up syntax-rules. If they don't load up syntax-rules, they can't
define macros (barring defmacro which is not R5RS), and without there's
no difference between load and load-for-syntax.

Also this runs into other issues:

    (define (my-load foo)
      (warn "something")
      (load foo))

Or

    (define (my-load2 foo)
      (load (frob foo)))

> What do you think?

If there is a sensible thing to do here, I'm happy to do it. But I don't
yet see what that thing is.

Andy
-- 
http://wingolog.org/




  reply	other threads:[~2009-09-03  8:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-29 15:49 Problems with LOAD and latest build Barry Fishman
2009-08-30 14:17 ` Andy Wingo
2009-08-30 15:54   ` Barry Fishman
2009-08-31  8:46   ` Ludovic Courtès
2009-09-03  8:43     ` Andy Wingo [this message]
2009-09-03 16:14       ` Ludovic Courtès

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=m34ork2zb8.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).