Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6178205
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T00:25:07+00:00 2026-05-24T00:25:07+00:00

Why is System.out.println(super) not permitted? System.out.println(this); This is OK and this.toString() is called and

  • 0

Why is System.out.println(super) not permitted?

System.out.println(this);

This is OK and this.toString() is called and printed automatically.
Of course, instance variable is OK instead of this.

However, this and super can be used in same way as I know.

System.out.println(super);

So why does this fail? I think it’s supposed to call super.toString() implicitly.
I have read Java specification document, but I haven’t found the reason.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-24T00:25:07+00:00Added an answer on May 24, 2026 at 12:25 am

    Implementing a standalone variant of super that breaks virtual method dispatch would be an extremely bad idea.

    Let’s think about it for a while.

    abstract class Base {
        abstract String Description();
        String toString() { return "Base"; }
    }
    class Derived extends Base {
        String Description() { return "Derived description"; }
        String toString() { return "Derived"; }
    
        static void use(Base instance) {
            System.out.println(instance.toString());
            System.out.println(instance.Description());
        }
    }
    

    Now, let us take your suggestion and suppose that super is valid and does what you suggest; then we may write in Derived:

    class Derived extends Base {
        // Previous declarations omitted.
        void useSuper() { Derived.use(super); }
        void useThis() { Derived.use(this); }
    
        static void main() {
            Derived instance = new Derived();
            instance.useThis();
            instance.useSuper();
        }
    }
    

    Now, if I understood you, you suggest that the main function should print in order:

    • the implementation of toString() from Derived: “Derived”.
    • the implementation of Description() from Derived: “Derived description”
    • the implementation of toString() from Base: “Base”.
    • the implementation of Description() from Base: It does not exist. And the two solutions I can think of leads to bigger problems:
      • Raise an exception: congratulations, you can now break any program which relies on abstract methods actually being implemented without even thinking about it. (How would you know that a function will call the abstract method?)
      • Return the implementation from Derived: breaks consistency.

    In short, such a use of the word super conceptually breaks object-oriented programming.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

class a{ public void foo(int a){ System.out.println(super); } } class b extends a{ public
System.out.println( Arrays.deepToString( abc<def>ghi.split((?:<)|(?:>)) ) ); This prints [abc, def, ghi] , as if I
This code: System.out.println(String.format(%f, Math.PI)); System.out.println(Math.PI); produces that result on my computer: 3,141593 3.141592653589793 Why
Could someone please explain why this happening: class Apple { String type; setType(){ System.out.println(inside
public class Common { public synchronized void synchronizedMethod1() { System.out.println(synchronizedMethod1 called); try { Thread.sleep(1000);
System.out.println(1+2+3); System.out.println(1+2+3); output:- 33 123 First case is understood but the second case is
System.out.println(matcher.group(1)); System.out.println(matcher.group()); I like to know what's the difference between the above two codes.
System.out.println(ganzeZeile[26]); System.out.println(filter.get(11)); System.out.println(ganzeZeile[26].contains(filter.get(11))); ganzeZeile is an array of Strings. filter is an ArrayList of
class A { void F() { System.out.println(a); }} class B extends A { void
Why does System.out.println(-1<<32) display -1 in Java? Is there any root cause? I hope

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.