NB Apologies for multiple posting. Previous message was too large.

Hi, Al,

I'm still not convinced that we cannot "view these concepts in terms of 
drawbacks and trade-offs".

Allow me to introduce an argument of reductio ad absurdum. If it is "difficult 
to find problems/trade-offs" with what you call the MDP, should not all our 
code 
look like:

public Object doSomething(Object object) { ... }
public Object doSomethingElse(Object object) { ... }
public Object doSomethingDifferent(Object object) { ... }

or similar? That is, at what point do we say a collection of methods taking an 
object and returning an object is not sufficient to describe our system?

Phill


      
_______________________________________________
patterns-discussion mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/patterns-discussion

Reply via email to