Steel Bank Common Lisp

Kevin,

Rather than using the deprecated 'require, it would be worth looking into
ASDF. I use that combined with a 'defun in my .sbclrc, which lets me
invoke (asdf-load :package) when I need to reload the whole thing.

If that's too much overhead, look at wrapping 'load around 'compile-file;
I did this myself until I discovered ASDF.

I know I'm answering questions other than the exact one you asked, but
hopefully those are better solutions to the problem at hand.


Cheers,
James


> Maybe a simple question but not obvious to me (as a beginner) how to
> do....
>
> How do i force reload of a package with the "require" function.  I am
> working on a cffi based foreign package in c and I don't want to
> continually have restart by sbcl repl when I make a change to my shared c
> library to test. Is there a way to set require to reload the library when
> it executes or some similar function. .?
>
> Thanks
>
> Sent from my iPad
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://ad.doubleclick.net/clk;226879339;13503038;l?
> http://clk.atdmt.com/CRS/go/247765532/direct/01/
> _______________________________________________
> Sbcl-help mailing list
> Sbcl-help@...
> https://lists.sourceforge.net/lists/listinfo/sbcl-help
>

Il giorno 27/lug/2010, alle ore 03.51, "James Fleming" <lisp@...> ha scritto:

> Kevin,
> 
> Rather than using the deprecated 'require, it would be worth looking into
> ASDF.


Isn't 'require equivalent to asdf:load-system in sbcl?

How about I send my reply to the entire list this time, instead of
directly to Giovanni?
*facepalm*


>> Rather than using the deprecated 'require, it would be worth looking
>> into ASDF.
>
>
> Isn't 'require equivalent to asdf:load-system in sbcl?

It _can_ be. I thought the answer was "hell no, they're different things,"
but the spec says that enough of its behaviour is implementation-specific
that it can default to using ASDF. According to Zach Beane, that's exactly
what SBCL does:
http://xach.livejournal.com/191187.html
I'll take his word for it, because I know that he knows a lot more about
this than I do.

However, I'm pretty sure that's exactly why it's deprecated: so much of
its behaviour is _defined_ as being implementation-specific that you can't
be sure that you've used it in a way that's portable.

If you're using it with the expectation that ASDF will be invoked under
the covers, you're better off making the assumption explicit, and calling
it directly. So much better than switching implementations two years from
now and wondering why your code is suddenly failing in unexpected ways.

Me, I just keep the following convenience function in my .sbclrc to save a
bit of typing:
(defun asdf-load (pkg)
  (asdf:oos 'asdf:load-op pkg))


Cheers,
James

On Tue, 27 Jul 2010 20:48:26 +1000, James Fleming wrote:

> Me, I just keep the following convenience function in my .sbclrc to save
> a bit of typing:
> (defun asdf-load (pkg)
>   (asdf:oos 'asdf:load-op pkg))

If you are using SLIME, you can save a lot of typing by using
,load-system in the REPL (has tab completion, so ,lo[TAB] is enough).
For the OP's problem, ,reload-system (or ,rel[TAB]) is the preferred
solution in SLIME.  System names are completed, too.  I could not
imagine anything more convenient.

Tamas

On 27 July 2010 13:48, James Fleming <lisp@...> wrote:

>> Isn't 'require equivalent to asdf:load-system in sbcl?

Yes and no. See:

  http://www.sbcl.org/manual/#Customization-Hooks-for-Users

SBCL itself does two things with REQUIRE:

 (1) Contrib modules are available using it.

 (2) After ASDF has been loaded, it delegates to ASDF:OOS 'LOAD-OP
     if the named module is known to ASDF.

Over the last few years similarly customizable REQUIRE has been
implemented by some other implementations as well.

I would say that REQUIRE is an excellent tool for REPL work, and even
for local scripting -- but using it in software ment to run on other
people's systems is a bad idea.

For the most part you should disregard the "deprecation" notes in
CLHS: REQUIRE isn't going anywhere, and neither is REMOVE-IF-NOT.
Really.

Neither should you be afraid of using "implementation specific"
functionality, unless you are writing a library intended to run on
multiple implementations.

Cheers,

 -- Nikodemus