From: Trans <transfire@...>
Date: 2007-01-01T11:17:30+09:00
Subject: Re: Little Things


Devin Mullins wrote:
> Trans wrote:
> > The main thing is that it creates an exception b/c we are forced to use
> > a reciever, eg. self.class, so it can't be called as a "function" nor
> > made private. No other method is like that.
> Actually, two classes of method names come to mind:
> - Those that share a name with a keyword (class, when, def, etc.)

That's a good point. Although 'when', 'def' and others aren't also
built-in methods. And in a private context at least, no one is going to
readily use them as such.

> - Setter methods (/=$/, that is)
>
> There's an exception for the latter -- when private, they can be called
> with self as an explicit receiver.

True. An expection I never liked, but it's neccessary, and at least
it's a very simple pattern.

> Neither defending the behavior nor arguing for a change... just playing
> Mr. Fact Checker (or Mr. Obvious, depending on your POV).

facts == good

Thanks,
T.