From: Steven Jenkins <steven.jenkins@...>
Date: 2005-06-21T00:08:49+09:00
Subject: Re: preventing instantiation

R. Mark Volkmann wrote:
> That does work, but I see two issues with that approach.
> 1) it adds an "instance" method that isn't useful and is misleading

You can get rid of it, just as you're getting rid of the "new" method 
you no longer want.

> 2) someone might think the class is a singleton when in fact it isn't

Ruby has the '#' construct for just this occasion :-)

But I agree, it's not pretty. You advanced quickly from needing *a* way 
to finding some ways wanting. :-)

Steve