in reply to Re^3: How A Technique Becomes Over-rated
in thread How A Function Becomes Higher Order

Sticking my nose in where it doesn't belong...

If I understand it right, one of the points of L~R's original post was that the comparison function can be defined by the user, and passed in as a coderef. If I understand your post, you seem to be saying that the same end result can be achieved through OO and classes.

But I'm fuzzy on what you suggest should happen in OO. If the class has a compare method that doesn't work for my current problem, do I subclass it and create my own maxstr? Do I append to the class my own method?

... package SomeClass; sub my_compare {...} ...
What if each object needs a unique compare function? What if these functions aren't known at compile time? What if there are so many functions that it's difficult to give them all unique and useful names?

I'm not sure that any of these questions are easier or harder to answer in OO vs. closures.

Quantum Mechanics: The dreams stuff is made of