I think that means that the JVM reads your code line by line and initialize the classes as needed, starting by your "Main" class. It only loads class A if your "Main" class has a reference to it, then stops loading the "Main" class and starts loading A, when A referrs to B, pauses the load of A and start with B, the resumes the load of A, and at last resumes the load of "Main".
On Thu, Jul 28, 2011 at 4:25 PM, RLScott <fixthatpi...@yahoo.com> wrote: > > > On Jul 28, 11:13 am, Daniel Drozdzewski <daniel.drozdzew...@gmail.com> > wrote: > > > > > > There is this paragraph: > > ' The static initializers and class variable initializers are executed > > in textual order, and may not refer to class variables declared in the > > class whose declarations appear textually after the use, even though > > these class variables are in scope (ยง8.3.2.3). This restriction is > > designed to detect, at compile time, most circular or otherwise > > malformed initializations.' > > Ah, that makes sense. Thank you. But what is the textual order when > my code is developed in Eclipse where my source Java files are listed > in alphabetical order, one class per file? Is that the textual order? > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
