[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Document the current module system?
From: |
Marius Vollmer |
Subject: |
Re: Document the current module system? |
Date: |
20 Apr 2001 19:50:02 +0200 |
User-agent: |
Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7 |
Rob Browning <address@hidden> writes:
> We should also have a section detailing the current preferred approach
> for creating modules with C shared library components. If no one else
> is interested, I'd be willing to give that a shot, if Marius can help
> make sure I'm getting it straight :>
Yes, yes. I wanted to document this for quite a while already, but it
had to compete with hacking on guile-lightning...
We should probably start with a list of ways that compiled code might
be used in relation to the module system, like:
- A module might be provided completely by compiled code.
- Compiled code might provide only part of a module.
- Compiled code might want to provide bindings only on demand (to save
initialization time) even if it has been linked already.
etc...
Document the current module system?, NIIBE Yutaka, 2001/04/19
- Re: Document the current module system?, Martin Grabmueller, 2001/04/19
- Re: Document the current module system?, Rob Browning, 2001/04/20
- Re: Document the current module system?, NIIBE Yutaka, 2001/04/23
- Re: Document the current module system?, NIIBE Yutaka, 2001/04/23
- Re: Document the current module system?, Martin Grabmueller, 2001/04/23
- Recursive namespace, Keisuke Nishida, 2001/04/23
- Recursive namespace, NIIBE Yutaka, 2001/04/23