static-initialization

Compiling / linking with -nostdlib seems to prevent static initialization, even if I add my own crti.s and crtn.s with .init / .fini sections. Are there workarounds to make g++ generate static initialization code that is inserted in .init or that I can call manually? This is what I tried: g++ -o test.o -c -fno-use-cxa-atexit test.cc # has _start (entry point) # that calls _init and _main as -o crti.o crti.s # has _init in section .init as -o crtn.o crtn.s g++ -o test ./crti.o test.o -nodefaultlibs -nostartfiles ./crtn.o -nodefaultlibs alone includes static initialization code and call, but

I have 2 classes: Class A: public class A { static B b = new B(); static { System.out.println("A static block"); } public A() { System.out.println("A constructor"); } } Class B: public class B { static { System.out.println("B static block"); new A(); } public B() { System.out.println("B constructor"); } } I create a Main class which just creates new A: public class Main { public static void main(String[] args) { new A(); } } The output I get is: B static block A constructor B constructor A static block A constructor As you can see, the constructor of A is invoked before its static initializer.

I wonder if it's reliable to use a construction like: private static final Map<String, String> engMessages; private static final Map<String, String> rusMessages; static { engMessages = new HashMap<String, String> () {{ put ("msgname", "value"); }}; rusMessages = new HashMap<String, String> () {{ put ("msgname", "значение"); }}; } private static Map<String, String> msgSource; static { msgSource = engMessages; } public static String msg (String msgName) { return msgSource.get (msgName); } Is there a possibility that I'll get NullPointerException because msgSource initialization block will be

I'm using a C++ library that can be built as either a shared or a static library. This library uses a factory technique, where static objects register themselves when the program starts and the static objects get created. This works fine as long as the shared library is used. When the static version is used, none of the static objects get included into the final program (because they aren't referenced directly) and thus their functionality isn't available. Is there a way to force gcc to include all static objects from a library when linking? The library is Open Source and I could modify it, if

What's the difference between initialization within a static block: public class staticTest { static String s; static int n; static double d; static { s = "I'm static"; n = 500; d = 4000.0001; } ... And individual static initialization: public class staticTest { static String s = "I'm static"; static int n = 500; static double d = 4000.0001; .... A static initialization blocks allows more complex initialization, for example using conditionals: static double a; static { if (SomeCondition) { a = 0; } else { a = 1; } } Or when more than just construction is required: when using a builder to

When I tried to write something like this: public interface MyInterface { static { System.out.println("Hello!"); } } the compiler could not compile it. But when I wrote something like this: interface MyInterface { Integer iconst = Integer.valueOf(1); } and decompiled it, I saw static initialization: public interface MyInterface{ public static final java.lang.Integer i; static {}; Code: 0: iconst_1 1: invokestatic #1; //Method java/lang/Integer.valueOf:(I)Ljava/lang/Integer; 4: putstatic #2; //Field i:Ljava/lang/Integer; 7: return } Could you please explain this behavior to me? You can have