Why can methods be overriden but attributes can't?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have a class
public class A {
public String attr ="A attribute";
public void method() {
System.out.println(this+" , "+this.attr);
}
public String toString() {
return("Object A");
}
}
and another class that inherits from it
public class B extends A{
public String attr = "B attribute";
public void method() {
super.method();
}
public String toString() {
return("Object B");
}
}
Note that the method() of B is simply a wrapper for method() of A.
When I run the following code
B b = new B();
b.method();
I get Object B , A attribute as output which means that, this and this.attr accessed different things. Why is that the case?
Shouldn't System.out.println(this) refer to the toString() method of class A ?
java inheritance this
edited Mar 28 at 20:00
Ondra K.
1,016726
asked Mar 27 at 14:44
Noah BishopNoah Bishop
1138
add a comment |
I have a class
public class A {
public String attr ="A attribute";
public void method() {
System.out.println(this+" , "+this.attr);
}
public String toString() {
return("Object A");
}
}
and another class that inherits from it
public class B extends A{
public String attr = "B attribute";
public void method() {
super.method();
}
public String toString() {
return("Object B");
}
}
Note that the method() of B is simply a wrapper for method() of A.
When I run the following code
B b = new B();
b.method();
I get Object B , A attribute as output which means that, this and this.attr accessed different things. Why is that the case?
Shouldn't System.out.println(this) refer to the toString() method of class A ?
java inheritance this
edited Mar 28 at 20:00
Ondra K.
1,016726
asked Mar 27 at 14:44
Noah BishopNoah Bishop
1138
1
A modern IDE will have the possibility to show a warning on the second definition ofattrthat it 'shadows' a similarly named field of a superclass.
– Mark Jeronimus
Mar 27 at 15:49
@Noah why did you revert the edited question name? I think the edited titleWhy can methods be overriden but attributes can'tdescribed the content of the question better than the current one. This is important for all other people looking for an answer to their question.
– Ondra K.
Mar 28 at 12:20
add a comment |
I have a class
public class A {
public String attr ="A attribute";
public void method() {
System.out.println(this+" , "+this.attr);
}
public String toString() {
return("Object A");
}
}
and another class that inherits from it
public class B extends A{
public String attr = "B attribute";
public void method() {
super.method();
}
public String toString() {
return("Object B");
}
}
Note that the method() of B is simply a wrapper for method() of A.
When I run the following code
B b = new B();
b.method();
I get Object B , A attribute as output which means that, this and this.attr accessed different things. Why is that the case?
Shouldn't System.out.println(this) refer to the toString() method of class A ?
java inheritance this
edited Mar 28 at 20:00
Ondra K.
1,016726
asked Mar 27 at 14:44
Noah BishopNoah Bishop
1138
I have a class
public class A {
public String attr ="A attribute";
public void method() {
System.out.println(this+" , "+this.attr);
}
public String toString() {
return("Object A");
}
}
and another class that inherits from it
public class B extends A{
public String attr = "B attribute";
public void method() {
super.method();
}
public String toString() {
return("Object B");
}
}
Note that the method() of B is simply a wrapper for method() of A.
When I run the following code
B b = new B();
b.method();
I get Object B , A attribute as output which means that, this and this.attr accessed different things. Why is that the case?
Shouldn't System.out.println(this) refer to the toString() method of class A ?
java inheritance this
java inheritance this
edited Mar 28 at 20:00
Ondra K.
1,016726
asked Mar 27 at 14:44
Noah BishopNoah Bishop
1138
edited Mar 28 at 20:00
Ondra K.
1,016726
asked Mar 27 at 14:44
Noah BishopNoah Bishop
1138
edited Mar 28 at 20:00
Ondra K.
1,016726
edited Mar 28 at 20:00
Ondra K.
1,016726
edited Mar 28 at 20:00
Ondra K.
1,016726
1,016726
asked Mar 27 at 14:44
Noah BishopNoah Bishop
1138
asked Mar 27 at 14:44
Noah BishopNoah Bishop
1138
asked Mar 27 at 14:44
Noah BishopNoah Bishop
1138
1138
1
A modern IDE will have the possibility to show a warning on the second definition ofattrthat it 'shadows' a similarly named field of a superclass.
– Mark Jeronimus
Mar 27 at 15:49
@Noah why did you revert the edited question name? I think the edited titleWhy can methods be overriden but attributes can'tdescribed the content of the question better than the current one. This is important for all other people looking for an answer to their question.
– Ondra K.
Mar 28 at 12:20
add a comment |
1
A modern IDE will have the possibility to show a warning on the second definition ofattrthat it 'shadows' a similarly named field of a superclass.
– Mark Jeronimus
Mar 27 at 15:49
@Noah why did you revert the edited question name? I think the edited titleWhy can methods be overriden but attributes can'tdescribed the content of the question better than the current one. This is important for all other people looking for an answer to their question.
– Ondra K.
Mar 28 at 12:20
1
1
A modern IDE will have the possibility to show a warning on the second definition of
attr that it 'shadows' a similarly named field of a superclass.– Mark Jeronimus
Mar 27 at 15:49
A modern IDE will have the possibility to show a warning on the second definition of
attr that it 'shadows' a similarly named field of a superclass.– Mark Jeronimus
Mar 27 at 15:49
@Noah why did you revert the edited question name? I think the edited title
Why can methods be overriden but attributes can't described the content of the question better than the current one. This is important for all other people looking for an answer to their question.– Ondra K.
Mar 28 at 12:20
@Noah why did you revert the edited question name? I think the edited title
Why can methods be overriden but attributes can't described the content of the question better than the current one. This is important for all other people looking for an answer to their question.– Ondra K.
Mar 28 at 12:20
add a comment |
1 Answer
1
active
oldest
votes
By declaring a method with a same name as parent class, you override it, that is, replace the original behaviour. But if you declare a field with a same name, you effectively hide it, making it inaccessible from that subclass, but only by super.field. See oracle docs on variable hiding, as well as using the keyword super. Note that it is not recommended to use variable hiding, as it creates exactly the kind of confusion you're experiencing.
By calling super.method(), printing this results in calling the toString method, which was in fact overridden - so that's the reason why it prints "Object B", as you've called the method on an instance of B. But the this in this.attr actually refers to the parent object, as you're calling the method from the parent class (by super.method()).
answered Mar 27 at 14:49
Ondra K.Ondra K.
1,016726
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55380016%2fwhy-can-methods-be-overriden-but-attributes-cant%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
By declaring a method with a same name as parent class, you override it, that is, replace the original behaviour. But if you declare a field with a same name, you effectively hide it, making it inaccessible from that subclass, but only by super.field. See oracle docs on variable hiding, as well as using the keyword super. Note that it is not recommended to use variable hiding, as it creates exactly the kind of confusion you're experiencing.
By calling super.method(), printing this results in calling the toString method, which was in fact overridden - so that's the reason why it prints "Object B", as you've called the method on an instance of B. But the this in this.attr actually refers to the parent object, as you're calling the method from the parent class (by super.method()).
answered Mar 27 at 14:49
Ondra K.Ondra K.
1,016726
add a comment |
By declaring a method with a same name as parent class, you override it, that is, replace the original behaviour. But if you declare a field with a same name, you effectively hide it, making it inaccessible from that subclass, but only by super.field. See oracle docs on variable hiding, as well as using the keyword super. Note that it is not recommended to use variable hiding, as it creates exactly the kind of confusion you're experiencing.
By calling super.method(), printing this results in calling the toString method, which was in fact overridden - so that's the reason why it prints "Object B", as you've called the method on an instance of B. But the this in this.attr actually refers to the parent object, as you're calling the method from the parent class (by super.method()).
answered Mar 27 at 14:49
Ondra K.Ondra K.
1,016726
add a comment |
By declaring a method with a same name as parent class, you override it, that is, replace the original behaviour. But if you declare a field with a same name, you effectively hide it, making it inaccessible from that subclass, but only by super.field. See oracle docs on variable hiding, as well as using the keyword super. Note that it is not recommended to use variable hiding, as it creates exactly the kind of confusion you're experiencing.
By calling super.method(), printing this results in calling the toString method, which was in fact overridden - so that's the reason why it prints "Object B", as you've called the method on an instance of B. But the this in this.attr actually refers to the parent object, as you're calling the method from the parent class (by super.method()).
answered Mar 27 at 14:49
Ondra K.Ondra K.
1,016726
By declaring a method with a same name as parent class, you override it, that is, replace the original behaviour. But if you declare a field with a same name, you effectively hide it, making it inaccessible from that subclass, but only by super.field. See oracle docs on variable hiding, as well as using the keyword super. Note that it is not recommended to use variable hiding, as it creates exactly the kind of confusion you're experiencing.
By calling super.method(), printing this results in calling the toString method, which was in fact overridden - so that's the reason why it prints "Object B", as you've called the method on an instance of B. But the this in this.attr actually refers to the parent object, as you're calling the method from the parent class (by super.method()).
answered Mar 27 at 14:49
Ondra K.Ondra K.
1,016726
edited Mar 27 at 15:15
answered Mar 27 at 14:49
Ondra K.Ondra K.
1,016726
answered Mar 27 at 14:49
Ondra K.Ondra K.
1,016726
answered Mar 27 at 14:49
Ondra K.Ondra K.
1,016726
1,016726
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55380016%2fwhy-can-methods-be-overriden-but-attributes-cant%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
A modern IDE will have the possibility to show a warning on the second definition of
attrthat it 'shadows' a similarly named field of a superclass.– Mark Jeronimus
Mar 27 at 15:49
@Noah why did you revert the edited question name? I think the edited title
Why can methods be overriden but attributes can'tdescribed the content of the question better than the current one. This is important for all other people looking for an answer to their question.– Ondra K.
Mar 28 at 12:20