Good case for Singletons?

Question

I have an application that has several classes used for storing application-wide settings (locations of resources, user settings, and such). Right now these classes are just

Answer 1

Since your class is holding global settings, a pro for a singleton could be that you have more control about creation of the singleton. You could read a configuration file during object creation.

In other cases if methods are static there would be no benefit like in javas Math class which has only static members.

A more obvious need for singletons is when you implement factories as singletons, because you can interchange different implementations of this factory.