[src/trunk]: src/doc Expand discussion a bit, and provide ppp as an example w...

[pgoyette <pgoyette%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/25a6babc1f75
branches:  trunk
changeset: 346896:25a6babc1f75
user:      pgoyette <pgoyette%NetBSD.org@localhost>
date:      Sat Aug 06 00:30:57 2016 +0000

description:
Expand discussion a bit, and provide ppp as an example way to do things.

diffstat:

 doc/TODO.modules |  11 +++++++++--
 1 files changed, 9 insertions(+), 2 deletions(-)

diffs (25 lines):

diff -r 8d6ca83447de -r 25a6babc1f75 doc/TODO.modules
--- a/doc/TODO.modules  Sat Aug 06 00:02:33 2016 +0000
+++ b/doc/TODO.modules  Sat Aug 06 00:30:57 2016 +0000
@@ -1,4 +1,4 @@
-/* $NetBSD: TODO.modules,v 1.4 2016/08/05 04:21:01 pgoyette Exp $ */
+/* $NetBSD: TODO.modules,v 1.5 2016/08/06 00:30:57 pgoyette Exp $ */
 
 Some notes on the limitations of our current (as of 7.99.35) module
 subsystem.  This list was triggered by an Email exchange between
@@ -16,7 +16,14 @@
 
        There are ways around this (such as, having the parent
        module's initialization command recursively call the module
-       load code), but they're gross hacks.
+       load code), but they're often gross hacks.
+
+       Another alternative (which is used by ppp) is to provide a
+       "registration" mechanism for the "child" modules, and then when
+       the need for a specific child module is encountered, use
+       module_autoload() to load the child module.  Of course, this
+       requires that the parent module know about all potentially
+       loadable children.
 
 2. Currently, config(1) has no way to "no define" drivers