From: Andy Wingo <wingo@pobox.com>
To: Ramakrishnan Muthukrishnan <vu3rdd@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: reload-module usage
Date: Fri, 19 Nov 2010 16:47:49 +0100 [thread overview]
Message-ID: <m3lj4p2u3e.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTimRauV0w7qUQyYbJ1ZL6274zqcJmcEmiDLSh1ku@mail.gmail.com> (Ramakrishnan Muthukrishnan's message of "Fri, 19 Nov 2010 20:47:29 +0530")
On Fri 19 Nov 2010 16:17, Ramakrishnan Muthukrishnan <vu3rdd@gmail.com> writes:
> On Fri, Nov 19, 2010 at 11:57 AM, Ramakrishnan Muthukrishnan
> <vu3rdd@gmail.com> wrote:
>>
>>> (reload-module (tekuti boot))
>> <stdin>:18:15: warning: possibly unbound variable `tekuti'
>> <unnamed port>:18:16: In procedure module-lookup:
>> <unnamed port>:18:16: Unbound variable: tekuti
>>
>> Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
>
> `reload-module' is indeed a function which explains the error. How do
> we specify a module name?
It is a function that takes a module as an argument.
(reload-module (resolve-module (tekuti boot)))
would be how to use it. I'll add a REPL meta-command that takes a
name. Having the core procedure take a module instead of a name takes
away an error case -- what if it wasn't loaded before, do we load it for
the first time?
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-11-19 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 6:27 reload-module usage Ramakrishnan Muthukrishnan
2010-11-19 15:17 ` Ramakrishnan Muthukrishnan
2010-11-19 15:47 ` Andy Wingo [this message]
2010-11-19 15:46 ` Ramakrishnan Muthukrishnan
2010-11-19 15:50 ` Andy Wingo
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=m3lj4p2u3e.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=vu3rdd@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).