On Apr 6, 2004, at 5:12 PM, Andreas Raab wrote:

> However, when we look at "alternative implementations of the same 
> concepts"
> such as Morphic vs. MVC vs. Tweak as UI frameworks or Squeak's streams 
> vs.
> Flow there are conceptual conflicts which should make it very hard to 
> "reuse
> a name from a conflicting concept". Say, if I write a Morphic app and 
> I just
> happen to use the name "Switch" which is NOT defined in Morphic but IS
> defined in MVC I should not be able to do this because although there 
> *may*
> be a class called Switch it is not part of the context I am working in 
> -
> there is no working "Switch" class in the context of Morphic so 
> allowing
> users to use that name is simply introducing confusion. Similarly, just
> because Flow may not have a class called "WriteStream" doesn't mean 
> that you
> should mix up the concepts - if Flow says it captures the concept of
> streaming and other IO, then clearly the use of "WriteStream" in the 
> context
> of using Flow is just a complete confusion of concepts and should be 
> avoided
> at all costs.

+1

Thanks, Andreas - this is what was bothering me about the "optimistic 
importing" advocated in much of this thread, but haven't been able to 
articulate.

Avi