Re: [MiNT] WCOWORK vs WINDOM for components

[Jo Even Skarstein <joska@online.no>]

> -----Original Message-----
> From: mint-bounce@lists.fishpool.fi
> [mailto:mint-bounce@lists.fishpool.fi]On Behalf Of
> evan@coolrunningconcepts.com
> Sent: Saturday, July 23, 2005 6:12 AM
>
> You don't understand.  I WANT to use WCOWORK.  I like it.  But
> you cannot be
> guaranteed that you have the source for all libraries you link
> with.  There is
> something called "modularity", and if done properly, what one module
> does won't
> interfere with the other.  WCOWORK breaks that simple fundamental
> principle
> since as soon as you set that mode for one module, the API of
> other modules
> changes.  More advanced applications might have dozens of libraries and

I'd say you don't understand the concept of modularity at all. WCOWORK or
not - as long as each module has a clearly defined and documented interface,
you can do whatever you want inside of it! So module X decides to use
WCOWORK while module Y doesn't. So what? Module X must adapt it's data
before exporting them. Where's the problem?? Aren't the interfaces defined?
Does any of the modules depend on internal data or functionality in other
modules? Doesn't sound very modular to me then...

Jo Even