Re: [clisp-list] Re: Building CLISP for Windows: modules

[Sam S. <sd...@gn...>]

> * In message <DFD875E85664D3118FA6080006277DE70521652A@U8PN2.blf01.telekom.de>
> * On the subject of "[clisp-list] Re: Building CLISP for Windows: modules"
> * Sent on Mon, 11 Mar 2002 11:01:18 +0100
> * Honorable "Hoehle, Joerg-Cyril" <Joe...@t-...> writes:
>
> No, modules are usable on MS-Windows as well, even if possibly nobody
> ever did so. It's independent from the ability to load shared
> libraries via LoadLibrary() libtool, or dynload_modules. I built a
> module last week and wrote a nearly finished article this weekend,
> documenting how CLISP modules work and how to put them to use.

great!

> BTW, what's a good place to publish CLISP documentation or CLISP
> specific articles? I feel this is too specific for the cookbook.

this should go into the impnotes.
please see doc/impext.xml.

> > would you like to do this?
> As I've laid out in my article on FFI design (a few people received
> drafts), I consider the addition of a dynamic loading facility and API
> not a trivial concept to define. Implementaion would be easy. There
> have been thoughts on this five years ago, and again in 1999. Nothing
> usable came yet out of this... Maybe I should take a worse is better
> approach -- again.

I take it for a "yes" and awaiting patches. :-)

-- 
Sam Steingold (http://www.podval.org/~sds) running RedHat7.2 GNU/Linux
Keep Jerusalem united! <http://www.onejerusalem.org/Petition.asp>
Read, think and remember! <http://www.iris.org.il> <http://www.memri.org/>
Don't hit a man when he's down -- kick him; it's easier.