dblack / wobblini.net wrote:
> Hi --
>
> On Fri, 11 Aug 2006, Tim Pease wrote:
>
> > Should we ask Matz to rename the singleton to the "nonce"?  How about
> > a new keyword for referring to the singleton ...
> >
> > class << self
> >  ...
> > end
> >
> > becomes
> >
> > nonce self do
> > ...
> > end
> >
> > how about
> >
> > module Kernel
> > def nonce( arg, &block )
> >   n = class << arg; self end
> >   return n.class_eval(&block) if block_given?
> >   n
> > end
> > end
> >
> >
> > I do like the word, though -- etymology is fun!
>
> The problem with it for singleton class is that it is really a time
> word.  It suggests "for now", whereas a singleton class can be
> accessed repeatedly.  It's kind of the same problem as "ad hoc", since
> if you use a singleton class twice, it's not for one particular
> purpose.

An occassion need not be limited to an instantaneous moment. Could I
not say, "I have occassion for an Eigenclass"? It also has other
connotations, such as "need".

I don't think any word is ever going to be perfect, precisely becuase
there is no precise word for it. We have to define one. And the problem
with "singleton" is that it's already taken.

T.