Re: Multiple dispatch

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Wed, 15 Jun 2011 13:10:50 +0200, Yannick Duchêne (Hibou57)  
<yannick_duchene@yahoo.fr> a écrit:
> A common and simple example, while not related to dispatching, is stream  
> operations : although its clear a input/ouput method must have two  
> arguments, one for the stream and one for the data, how do you decide  
> the operation belongs to the package defining the type or to the package  
> defining the stream.
I forget to say there is another alternative to that kind of ambiguity :  
defining a third package. In that third package, both the stream type and  
the data type are treated equally, this is the package which represent the  
union or collaboration of both together, with no one of both looking like  
dominated or controlled by the other (because there is no reason for the  
design to act as if this was, as it is not). This obviously applies even  
better when there are more than two types involved (but the question most  
commonly raises when there are two types).


-- 
“Syntactic sugar causes cancer of the semi-colons.”  [Epigrams on  
Programming — Alan J. — P. Yale University]
“Structured Programming supports the law of the excluded muddle.” [Idem]
“c++; /* this makes c bigger but returns the old value */” [Anonymous]