|
modulemanager 1.0.0
Finds, loads and keeps track of modules at runtime
|
Finds, loads and keeps track of modules at runtime.
Split out of imodule: that repo holds the interface a module answers to, this one holds the machinery that loads them. An interface and a manager are two different jobs.
ModuleManager — the table of loaded modules. One row per shared library, one column per contract.SharedLibrary — a dlopen/dlsym wrapper, RAII, cross-platform.Stride — the two-axis table ModuleManager is built on. Generic: rows carry an identity, columns carry optional values.A loaded library IS a row, a contract IS a column, a module is the cell where they meet. Two identifiers, one per axis :
Load() names a row,T names a column.Both are yours. The manager never reads IModule::name() or type() — a module's address is its position in the table, not something it declares about itself. Those two stay on the module for whoever needs them, typically a plugin host that has no static types to work with.
Partial coverage is not an error : a vendor that only does 2D simply leaves the 3D column empty, and Get returns nullptr.
Find(key) hands back the row itself, so Get<T>(entity) and Get(entity) can work on it without looking the key up again.