Constructors

[Parimala Somasundaram]

What is the effect of compiling the following code and then executing the 'Child' application?
1. public class Papa {
2. int i;
3. Papa(int j) {i=j;}
4. }
5.
6. class Child extends Papa {
7. Child() {i=5;}
8. public static void main(String[] args) {
9. new Child();
10. }
11. }
A. Compiler error at line 6.
B. Compiler error at line 7.
C. Compiler error at line 9.
D. The code compiles but throws exception when the application is executed.
E. The code compiles and executes with no problems.
The answer is B. I can understand this. Since 'Papa' has non-default constructor, it does not get a no-parameter constructor at compile time. So line 7 will not compile, as the compile tries to call its superclass default constructor.
My question is: Will it compile if line 7 was:
Child(int k) { // do something
}
Does the compiler try to call the superclass no-parameter constructor only if the Child class has a no-parameter constructor?

[Jini Varghese]

Hello,
I think it will not. Try the code to confirm. Just changing the constructor to
Child(int j) {i=5;} will not remove the compiler error. Since the base class constructor takes an arg. and the base class does not have no-arg constructor, You have to explicitly call that,
super(6);
So the new form of Child constructor is:
Child(int j) {
super(j);
i=5;
}
The above is one way to remove the compiler error.
The other way is by giving the base class a non-arg constructor.
Please somebody tell if I am wrong.....

[Manfred Leonhardt]

Hi Parimala,
An easy way to think of it is:
JVM:
All class constructors will have a first line that contains a call to the method super().
Therefore, if you don't type it in then the compiler will place the following line as the new first line in ALL class constructors:
super(); // New first line provided by your friendly Java compiler!
Regards,
Manfred.

[Parimala Somasundaram]

Thanks Manfred, Jini.