Re: [MiNT] WCOWORK vs WINDOM for components

[evan@coolrunningconcepts.com]

Quoting Jo Even Skarstein <joska@online.no>:

> I'd say you don't understand the concept of modularity at all. WCOWORK or

Think so?

> not - as long as each module has a clearly defined and documented interface,

Yes!

> you can do whatever you want inside of it! So module X decides to use

That is the idea behind modularity!

> 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?

They should be!

> Does any of the modules depend on internal data or functionality in other
> modules? Doesn't sound very modular to me then...

Module X uses WCOWORK, Module Y does not.  Module Y calls wind_create()
expecting that wind_create() uses the FULL area of the window, but WCOWORK
being in effect means that all calls require the WORK area instead.  The API
changes!

Suddenly, how one module behaves DOES depend on what another module does!

So what breaks if we have seperate calls instead?