Is the Initialize-On-Demand idiom really necessary when implementing a thread safe singleton using static initialization, or would a simple static declaration of the instance suffice?
Simple declaration of instance as static field:
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - ...
I apologize if this question is too simple for the intermediate forum. Given the following code public class A { private String b = {"a", "b", "c", "d"}; private static A a = new A(); public static A getInstance() { return a; } int findGoofy(String x) { int j = -1; for (int i = 0; i < b.length; ++i) ...
I have had to master this technique to address some of the questions you mention. A singleton is a great way to keep track of global information, needed anywhere in your program. It is also a good place to put utilities and such so there won't be multiple copies of the same code. It's also the most over-used pattern in existence. ...
I have a static method which takes a few String and double parameters and contains only local variables. When it is called by multiple threads there seems to be an exception thrown intermittenly. I got a little paranoid and so I've changed it to an instance method, and now the problem seems to disappear. Is this just a coincidence? Is my ...