🚀 go-pugleaf

Hi Jack <g> (just realizing what this could mean)

I think that all techniques dealing with static methods do not create an
instance
of a class but do everything on the loaded class (only).

If you try a (Borland) DataModule you will see a technique to create just
one
instance of a class.

You would deal with such a class like you would do usually, e.g.
Single one = new Single();

They designed the constructor in a way that the first new would create that
single instance and all subsequent news will return the reference
of that first instance.
Look how they had done it!

Greetings
Michael

Jack Frosch <jackfrosch[NO SPAM]@mail.com> schrieb in im Newsbeitrag:
3b128359$1_1@dnews...
> IN their book "Design Patterns" the GoF defines the Singleton pattern's
> intent thus: "To ensure a class has only one instance, and provide a
global
> point of access to it."
>
> For Java implementations, I've seen two implementation variations to
achieve
> this:
>
> 1) Some people code all static methods and data in a class, thus ensuring
> only one "instance" of the class exists in the VM.
>
> 2) Others use an implementation where the class is defines as normal, but
> with a private constructor.  A single public, static method is provided to
> the single instance of the class that's stored as a private instance
> variable.
>
> Approach #2 clearly meets the pattern description of the GoF, but I'm
> wondering if there are any uniquely-Java reasons why approach #1 might be
> preferable?
>
> Thanks.
>
> Jack
>
>