Re: RFC 146 (v1) Remove socket functions from core

[David L. Nicol]

Nick Ing-Simmons wrote:

> We need to distinguish "module", "overlay", "loadable", ... if we are
> going to get into this type of discussion. Here is my 2¢:
> 
> Module   - separately distributable Perl and/or C code.  (e.g. Tk800.022.tar.gz)
> Loadable - OS loadable binary e.g. Tk.so or Tk.dll
> Overlay  - Tightly coupled ancillary loadable which is no use without
>            its "base"  - e.g. Tk/Canvas.so which can only be used
>            when a particular Tk.so has already be loaded.

I know I've got helium Karma around here these days but I don't like
"overlay" it is reminiscent of old IBM machines swapping parts of the
program out because there isn't enough core.  Linux modules have
dependencies on each other and sometimes you have to load the more basic
ones first or else get symbol-undefined errors.  So why not follow
that lead and call Overlays "dependent modules."

If a dependent module knows what it depends on, that module can be
loaded on demand for the dependent one.



-- 
                          David Nicol 816.235.1187 [EMAIL PROTECTED]
                                               Yum, sidewalk eggs!