is there any way to stop the compiler from calling a constructor implicitly?

[rahil.khan]

is there any way to compile a program without calling constructor.

[DarrylBurke]

Are you by any chance confusing compiling and executing?

db

[rahil.khan]

no i mean that whenever we compile the program an implicit constructor is called to that initializes all the non static variable to their default values, so i just want not to call that constructor either implicitly not explicitly, is there any way to do that?

[DarrylBurke]

No. When you compile a Java class, bytecode is generated. Nothing is 'called' or 'initialized.'

All fields, whether static or instance, have default values -- zero for numeric primitives, false for boolean and null for reference types.

I think you need to describe the problem for which you think a solution would be to not initialize variables.

db

[rahil.khan]

No. When you compile a Java class, bytecode is generated. Nothing is 'called' or 'initialized.'

All fields, whether static or instance, have default values -- zero for numeric primitives, false for boolean and null for reference types.

I think you need to describe the problem for which you think a solution would be to not initialize variables.

db

db have you ever open the bytecode? As per my knowledge all the non static variables are initialize with that implicit constructor, once i opened a bytecode and there was a constructor which i didn't define. so it mean that constructor must be there for some reasons, i don't exactly for what?

[gimbal2]

You're miswriting and misreading - DB is pointing out that the compiler does not call any constructor like you said in post 3. It may generate one if you don't provide any constructor yourself and that generated constructor may indeed at some point in time be called - when the application is being executed by the Java runtime, long after everything is compiled and packaged.

[rahil.khan]

ok sorry db but thank you both of you, but my question is still the same that implicit constructor, i don't want that constructor to be called at any point, Is there any way to skip it?

[JosAH]

ok sorry db but thank you both of you, but my question is still the same that implicit constructor, i don't want that constructor to be called at any point, Is there any way to skip it?

That 'implicit constructor' as you call it, is it named '<cinit>'? or '<init>'?

kind regards,

Jos

[Tolls]

Since all classes in Java ultimately extend from Object then, without at least an implicit constructor call, how do you expect the underlying Object structure to be initialised?

[gimbal2]

ok sorry db but thank you both of you, but my question is still the same that implicit constructor, i don't want that constructor to be called at any point, Is there any way to skip it?

Yes you do - it is not Java that needs to be corrected here, it is your expectations and understanding of the situation. I'm going to not beat around the bush in the next sentence, beware:

If you have a code design that becomes problematic because Java is performing a vital function of the platform, then change your code design so it doesn't suck anymore.

[jim829]

Instead of asking questions whether Java or the compiler can do this or that, why not tell use why you want to do it. Perhaps we can offer a better solution.

Regards,
Jim

[rahil.khan]

you are getting me wrong i just want to know whether we can do that or not, by all your last replies its clear that there no way to skip it. Thank you so much guys... its always very helpful to be here... and going through this forum is just awesome...