On 2/13/2011 4:10 PM, David T. Lewis wrote:
> p.s. There is currently a similar debate under way on the Pharo list
> concerning #caseOf: and #caseOf:otherwise:. It appears that these two
> methods have been living quiet and and productive lives for many years
> within the community, albeit largely unnoticed by their neighbors.
> Recently however, they have been exposed as idiologically impure,
> and there is now an angry mob at the gates of the palace demanding
> extermination of these impostors to object-oriented correctness. A
> couple of people have vainly attempted to calm the public outrage by
> defending the utility and harmless demeanor of these methods, but
> they in turn are seen as apologists for the guilty, evidence perhaps
> of a broader conspiracy. This is not a story that is likely to end
> well, although I recommend it as an entertaining read for those with
> a sense of humor. The tale begins here:
>
>   http://lists.gforge.inria.fr/pipermail/pharo-project/2011-February/042064.html

Ah, an epic clash between purists and pragmatists. I'm with the 
pragmatists in both cases; I value my case statement in the right 
situations (dictionary dispatch is a VERY poor replacement) and I like 
the idea of Object>>is: for sake of not having to pollute the Object 
namespace. But that's just my $.02 :-)

Cheers,
   - Andreas