James wrote:
> i'm going to write a program and what i'd like is to have a kernel that
> takes care of memory management and other boring stuff and then have separate
> modules/plugins that actually do things (so there could be a networking
> module which handled all networking functions, a sound module which handled
> sound... etc). Sort of like the kernel and plugins for gimp/premiere/photoshop/
> whatever.
>
> the question being... how? (cos somehow the kernel would need to know what
> is in each module without having that info hard coded into it)
See the dlopen(3) manpage.
--
Glynn Clements <[EMAIL PROTECTED]>
