Re: [MiNT] WCOWORK vs WINDOM for components

[evan@coolrunningconcepts.com]

Quoting Joakim Högberg <gokmase@gmail.com>:

> Shouldn't these modules be able to receive and pass information on 
> what mode the main
> program is running in?

Tell your computer science teacher you designed a system where the 
parameters to
your API change depending on a mode that not every module might 
support, but you
pass around the mode.

Not a consistent API.   BARF.  Only solution is to make sure no modules in the
system use WCOWORK, or make sure none of them DON'T use it.

Back to the idea of overloading SHM with a plugin namespace, you'd have 
WCOWORK
and non-WCOWORK paths to separate the modules that can be loaded, and you'd
better check the docs for anything you link with.