Re: Have a problem with static

From:

Daniel Pitts <newsgroup.spamfilter@virtualinfinity.net>

Newsgroups:

comp.lang.java.programmer

Date:

Tue, 26 Feb 2008 12:55:05 -0800

Message-ID:

<47c47ca2$0$28623$7836cce5@newsrazor.net>

Lord Zoltar wrote:

Sreenivas wrote:

Dear friends,
                I have a problem with static concept . The code as
follows,
             1) static{
                      int k=10;
                     String j="India";
                        }
               2)
                      static int k=10;
                      static String j="India";

             is it both code segments equal?
Thanks & Regards,
Sreenivas Reddy Thatiparthy.

In this case, yeah they do pretty much the same thing.
BUT....

*bzzt* wrong...
class Foo {
static {int foo = 3}
static int bar = 3;
}

Foo.foo will not exist, Foo.bar will.

the "static {...}" form provides a way to execute code inside of a class
initialization. the "static int ..." form creates a class-level variable.

with a static BLOCK you could do fancier things:
static
{
    String j = "India"
    for (int i = 0; i<j.length(); j++)
    {
        System.out.println("You can only do this sort of thing in a
static block!");
    }
    try
    {
        Connection c = new DBConnection("Some:db:url");
    }
    catch (Exception e)
    {
        System.out.println("Error creating connection!");
    }
}

....Ok, not the greatest example, but it illustrates that you can have
other blocks of code inside a static initializer. The loop and the try/
catch cannot be done with the style in (2) in your examples.
Personally, I try to avoid static initializers when possible, and do
that work in constructors.

--
Daniel Pitts' Tech Blog: <http://virtualinfinity.net/wordpress/>