unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: Difference Between REPL and Script Usage?
Date: Sun, 30 Jan 2011 13:21:24 +0100	[thread overview]
Message-ID: <m3sjwa1t17.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTikKh6UwsfVuYGNga7gWJ0oUNR3ygvf21uwAcku2@mail.gmail.com> (Noah Lavine's message of "Sat, 29 Jan 2011 12:38:16 -0500")

On Sat 29 Jan 2011 18:38, Noah Lavine <noah.b.lavine@gmail.com> writes:

> ./check-guile peg.test
> ;;; note: source file /Users/noah/Desktop/guile/guile/module/ice-9/peg.scm
> ;;;       newer than compiled
> /Users/noah/Desktop/guile/guile/cache/guile/ccache/2.0-0.T-LE-8/Users/noah/Desktop/guile/guile/module/ice-9/peg.scm.go

Here, this indicates that we are interpreting peg.scm.

> ERROR: Unbound variable: safe-bind-f

So somehow under interpretation, peg.scm relies on the value of
something that isn't defined yet.

BTW: when you submit your peg.scm patches, can you rebase them on top of
wip-mlucy?  That is mlucy's changes, but rebased onto a master of a few
days ago.

> But got an error. To see what was wrong, I opened guile and did
> "(use-modules (ice-9 peg))". That worked fine.

That probably auto-compiled peg.scm, then ran it.

> noah-lavines-macbook:guile noah$ ./check-guile peg.test

And now the test suite worked, as it was using the compiled peg.scm.

I think it's one of your standard eval-when style bugs.  Unfortunately
backtraces from interpreted code are currently terrible.

Regards,

Andy
-- 
http://wingolog.org/



      reply	other threads:[~2011-01-30 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29 17:38 Difference Between REPL and Script Usage? Noah Lavine
2011-01-30 12:21 ` 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=m3sjwa1t17.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=noah.b.lavine@gmail.com \
    /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).