On Wednesday, December 11, 2002, at 05:21  PM, Michael G Schwern wrote:

On Wed, Dec 11, 2002 at 04:56:03PM -0800, Michael Lazzaro wrote:
First, universal operators and universal methods both pollute the
useful (programmer) namespace to nearly the same extent.
Most of the methods are not universal.  For example:

     $foo.compress

would be in the String class, not Object (or whatever we're calling the
Right, I just wanted to clarify. Because deciding between, say:

$foo.sameas($bar); # universal method

$foo === $bar; # universal operator

would be a false savings. If a method _is_ universal, especially if it's symmetric, it might be an OK candidate for a builtin or operator. And if it isn't universal, I can see (almost) no justification for wasting an op on it, no matter how common it is.

(Again, though, C<$foo.id == $bar.id> is OK by me.)

MikeL

Reply via email to