Top OOPS concept interview questions to get hired Top OOP concepts | Page 4

over-burdening, however it has to know article to settled abrogated
technique calls. This graph clarifies the distinction great, however:
Would we be able to over-burden a static technique in Java?
Indeed, you can over-burden a static technique in Java. You can
announce the same number of static strategies for a similar name as
you wish gave every one of them have distinctive technique marks. See
the response for progressively point by point clarification and code
model.
Would we be able to abrogate static technique in Java?
No, you can't supersede a static technique since it's not limited to an
article. Rather, static techniques have a place with a class and settled at
gather time utilizing the sort of reference variable. However, Yes, you
can proclaim a similar static strategy in a subclass, that will result in
technique concealing for example in the event that you utilize reference
variable of sort subclass, at that point new technique will be called, yet
on the off chance that you utilize reference variable of superclass than
old strategy will be called.
Would we be able to avert superseding a technique without utilizing
the last modifier?
Indeed, you can avert the strategy abrogating in Java without utilizing
the last modifier. Truth be told, there are a few different ways to achieve
it for example you can check the strategy private or static, those can't be
abrogated.
Would we be able to supersede a private strategy in Java?
No, you can't. Since the private strategy is just available and obvious
inside the class they are pronounced, it's impractical to supersede them
in subclasses. However, you can abrogate them inside the internal class
as they are available there.