From mint-bounce@lists.fishpool.fi Sat Jul 23 21:59:58 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <20050723135717.kgofd2dvjin4g8gc@coolrunningconcepts.com> Date: Sat, 23 Jul 2005 13:57:17 -0600 From: evan@coolrunningconcepts.com To: gokmase@gmail.com Cc: Jo Even Skarstein , "mint@fishpool.com" Subject: Re: [MiNT] WCOWORK vs WINDOM for components References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) H3 (4.0) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - esc14.midphase.com X-AntiAbuse: Original Domain - fishpool.com X-AntiAbuse: Originator/Caller UID/GID - [32001 502] / [47 12] X-AntiAbuse: Sender Address Domain - coolrunningconcepts.com X-Source: X-Source-Args: X-Source-Dir: X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: evan@coolrunningconcepts.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-0.3 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00, NO_REAL_NAME X-Spam-Level: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id j6NJxviQ029858 Quoting Joakim Högberg : > 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.