Computer scienceProgramming languagesJavaCode organizationDesign patternsCreational patterns

Singleton

Bad singleton

Report a typo

Look at this unfortunate singleton implementation:

class BadSingleton {
    
    private static BadSingleton instance;
    
    public static BadSingleton getInstance1() {
        if (instance == null) {
            instance = new BadSingleton();
        }
        return instance;
    }
    
    public static BadSingleton getInstance2() {
        return new BadSingleton();
    }
}

What are the problems (excluding thread-safety)?

Select one or more options from the list

The method getInstance1 breaks the pattern.

The field instance must be declared as non-static.

The method getInstance2 breaks the pattern.

The constructor should be hidden (declared as private).

___

Create a free account to access the full topic