[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: reload-module usage
From: |
Ramakrishnan Muthukrishnan |
Subject: |
Re: reload-module usage |
Date: |
Fri, 19 Nov 2010 21:16:12 +0530 |
On Fri, Nov 19, 2010 at 9:17 PM, Andy Wingo <address@hidden> wrote:
> On Fri 19 Nov 2010 16:17, Ramakrishnan Muthukrishnan <address@hidden> writes:
>
>> On Fri, Nov 19, 2010 at 11:57 AM, Ramakrishnan Muthukrishnan
>> <address@hidden> 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?
Thanks Andy.
--
Ramakrishnan