Thursday, December 27, 2007

Faiz Ahmed Faiz

moti ho keh sheesha, jaam keh dur
jo toot gaya, so toot gaya
kab ashko.n say jur sakta hai
jo toot gaya, so choot gaya

tum nahaq tukray chun chun kar
daman mai.n chupaye baithay ho
sheesho.n ka maseeha koi nahi
kiya aas lagaye baithay ho

shayad keh inhi.n tukro.n mai.n kahi.n
woh saghir-e-dil hai jis mai.n kabhi
sad naz say utara karti thi
sehbay-e-gham-e-jana.n ki pari

phir duniya walo.n nay tum say
yeh saghar lay kar phor diya
jo maiy thi, baha di mitti mai.n
mehma.n ka shehpar tor diya

yeh rangeen rezay hai.n shayad
un shokh bilori.n sapno.n kay
tum mast jawani mai.n jin say
khalwat ko sajya kartay thay

nadari, daftar bhook aur gham
in sapno.n say takratey rahey
be reham tha chomukh pathrao
yeh kaanch kay dhanchay kiya kartay

ya shayad in zarro.n mai.n kahi.n
moti hai tumhari izzat ka
woh jis say tumharay ijz par
shamshad qadro.n nay raksh kiya

is mal ki dhun mai.n phirtay thay
tajir bhi buhat, rehzun bhi kai
hai chor nagar, yaa.n muflis ki
gar jan bachi tou aan gai

yeh saghar sheeshay laal-o-guhr
salim hoo to qeemat patay hai.n
yu.n tukray tukray hoo to faqt
chubtay hai.n, lahoo rulwatay hai.n

tum nahaq tukray chun chun kar
daman mai.n chupaye baithay ho
sheesho.n ka maseeha koi nahi
kia aas lagaye baithay ho

yadoo.n kay garebano.n kay rafo
par dil ki guzr kab hoti hai
ik bakhia udhaira, aik siya
yu.n umr basr kab hoti hai

is kar geh hasti mai.n jaha.n
yeh saghar sheeshay dhaltay hai.n
har shay ka badal mil sakta hai
sub daman pur ho saktay hai.n

jo hath barhay yawar hai yeha.n
jo aankh uthay, wo bakhtawar
ya.n dhan dolat ka ant nahi
ho.n ghat mai.n lakh daku magar

kab loot jhapat say hasti ki
dukanai.n khali hoti hai.n
ya.n parbat parbat heeray hai.n
ya.n sagar sagar moti hai.n

kuch log hai.n jo is daulat par
parday lutkaye phirtay hai.n
har parbat ko, har sagar ko
neelam charhaye phirtay hai.n

kuch wo bhi hai.n jo lar bhar kar
yeh parday noch giratay hai.n
hasti ki uthai geero.n ki
har chal uljhaye jatey hai.n

in dono.n mai.n run parta hai
nit basti basti, nagar nagar
har basti ghar kay seenay mai.n
har chalti rah kay mathay par

yeh kalak bhartay phirtay hai.n
woh jot lagatay phirtay hai.n
yeh aag lagatay phirtay hai.n
woh aag bujhatay phirtay hai.n

sab saghar sheeshy, laal-o-guhr
is bazi mai.n bid jatay hai.n
utho sab khali hatho.n
us ran say bulawey atay hai.n

java

Initialization of Classes and Interfaces

Initialization of a class consists of executing its static initializers and the initializers for static fields (class variables) declared in the class. Initialization of an interface consists of executing the initializers for fields (constants) declared there.

Before a class is initialized, its superclass must be initialized, but interfaces implemented by the class are not initialized. Similarly, the superinterfaces of an interface are not initialized before the interface is initialized.

When Initialization Occurs

Initialization of a class consists of executing its static initializers and the initializers for static fields declared in the class. Initialization of an interface consists of executing the initializers for fields declared in the interface.

Before a class is initialized, its direct superclass must be initialized, but interfaces implemented by the class need not be initialized. Similarly, the superinterfaces of an interface need not be initialized before the interface is initialized.

A class or interface type T will be initialized immediately before the first occurrence of any one of the following:

  • T is a class and an instance of T is created.
  • T is a class and a static method declared by T is invoked.
  • A static field declared by T is assigned.
  • A static field declared by T is used and the reference to the field is not a compile-time constant. References to compile-time constants must be resolved at compile time to a copy of the compile-time constant value, so uses of such a field never cause initialization.

Invocation of certain reflective methods in class Class and in package java.lang.reflect also causes class or interface initialization. A class or interface will not be initialized under any other circumstance.

The intent here is that a class or interface type has a set of initializers that put it in a consistent state, and that this state is the first state that is observed by other classes. 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 . This restriction is designed to detect, at compile time, most circular or otherwise malformed initializations.

As shown in an example in, the fact that initialization code is unrestricted allows examples to be constructed where the value of a class variable can be observed when it still has its initial default value, before its initializing expression is evaluated, but such examples are rare in practice. (Such examples can also be constructed for instance variable initialization. The full power of the language is available in these initializers; programmers must exercise some care. This power places an extra burden on code generators, but this burden would arise in any case because the language is concurrent

Before a class is initialized, its superclasses are initialized, if they have not previously been initialized.

Thus, the test program:

class Super {
        static { System.out.print("Super "); }
}
class One {
        static { System.out.print("One "); }
}
class Two extends Super {
        static { System.out.print("Two "); }
}
class Test {
        public static void main(String[] args) {
               One o = null;
               Two t = new Two();
               System.out.println((Object)o == (Object)t);
        }
}

prints:

Super Two false

The class One is never initialized, because it not used actively and therefore is never linked to. The class Two is initialized only after its superclass Super has been initialized.

A reference to a class field causes initialization of only the class or interface that actually declares it, even though it might be referred to through the name of a subclass, a subinterface, or a class that implements an interface.

The test program:

class Super { static int taxi = 1729; }
class Sub extends Super {
        static { System.out.print("Sub "); }
}
class Test {
        public static void main(String[] args) {
               System.out.println(Sub.taxi);
        }
}

prints only:

1729

because the class Sub is never initialized; the reference to Sub.taxi is a reference to a field actually declared in class Super and does not trigger initialization of the class Sub.

Initialization of an interface does not, of itself, cause initialization of any of its superinterfaces.

Thus, the test program:

interface I {
        int i = 1, ii = Test.out("ii", 2);
}
interface J extends I {
        int j = Test.out("j", 3), jj = Test.out("jj", 4);
}
interface K extends J {
        int k = Test.out("k", 5);
}
class Test {
        public static void main(String[] args) {
               System.out.println(J.i);
               System.out.println(K.j);
        }
        static int out(String s, int i) {
               System.out.println(s + "=" + i);
               return i;
        }
}

produces the output:

1
j=3
jj=4
3
 

The reference to J.i is to a field that is a compile-time constant; therefore, it does not cause I to be initialized. The reference to K.j is a reference to a field actually declared in interface J that is not a compile-time constant; this causes initialization of the fields of interface J, but not those of its superinterface I, nor those of interface K. Despite the fact that the name K is used to refer to field j of interface J, interface K is not initialized.

Politics

ONE PICTURE BETTER THAN THOUSAND WORDS




17th December 2007
Outside Chief Justice House
Islamabad Pakistan

Cricket


Bradman Batting Technique




Bradman’s early development was shaped by the high bounce of the ball on matting over concrete pitches. He favored "horizontal-bat" shots (such as the hook, pull and cut) to deal with the bounce and devised a unique grip on the bat handle that would accommodate these strokes without compromising his ability to defend. Employing a side-on stance at the wicket, Bradman kept perfectly still as the bowler ran in. His backswing had a "crooked" look that troubled his early critics, but he resisted entreaties to change.

His backswing kept his hands in close to the body, leaving him perfectly balanced and able to change his stroke mid-swing, if need be. Another telling factor was the decisiveness of Bradman’s footwork. He “used the crease” by either coming metres down the wicket to drive, or playing so far back that his feet ended up level with the stumps when playing the cut, hook or pull.

Bradman’s game evolved with experience. He temporarily adapted his technique during the Bodyline series, deliberately moving around the crease in an attempt to score from the short-pitched deliveries. He had an ability to switch between a defensive or attacking innings as the occasion demanded, during the peak of his career in the mid-1930s. After the war, he readjusted to bat within the limitations set by his age, becoming a steady “accumulator” of runs.

However, Bradman never truly mastered batting on sticky wickets. Wisden commented, "if there really is a blemish on his amazing record it is... the absence of a significant innings on one of those 'sticky dogs' of old".

Blog Archive