What is wrong in the following code

Question

1.00/5 (1 vote)

See more:

Java

class Test{
public static void
main(String[]args){
A a=new A();
a.print();
}
}
class A{
String s;
A(String s){
this.s=s;
}
public void print(){
System.out.print(s);
}
}

What I have tried:

Java

class Test{
public static void
main(String[]args){
A a=new A();
a.print();
}
}
class A{
String s;
A(String s){
this.s=s;
}
public void print(){
System.out.print(s);
}
}

Posted 20-May-23 19:58pm

Etebarek G/meskel

Updated 20-May-23 20:49pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2023-05-20T20:49:00

Look at the constructor and the instance creation code:
Constructor:

Java

A(String s){
    this.s=s;
    }

Instance creation code:

Java

A a=new A();

The constructor requires a formal parameter - a String
But when you try to create the instance, you do not provide it.

The system can't find a constructor that takes no parameters - because when you explicitly add a constructor the system no longer builds a default no-parameter one for you - so you get an error.

Pass the constructor a String and it'll compile:

Java

A a=new A("Hello world!");

You should expect to get syntax errors every day, probably many times a day while you are coding - we all do regardless of how much experience we have! Sometimes, we misspell a variable, or a keyword; sometimes we forget to close a string or a code block. Sometimes the cat walks over your keyboard and types something really weird. Sometimes we just forget how many parameters a method call needs.

We all make mistakes.

And because we all do it, we all have to fix syntax errors - and it's a lot quicker to learn how and fix them yourself than to wait for someone else to fix them for you! So invest a little time in learning how to read error messages, and how to interpret your code as written in the light of what the compiler is telling you is wrong - it really is trying to be helpful!

So read this: How to Write Code to Solve a Problem, A Beginner's Guide Part 2: Syntax Errors[^] - it should help you next time you get a compilation error!

And spending a little time learning to understand syntax error messages will save you a huge amount of time in future: you waited at least 3/4 hour for this reply, then your email system probably added another 10 minutes or so, plus the time it took you to type up the question once you had found this site and created an account. Chances are that you could have saved a significant chunk of that time if you knew how to read them!

I'm not saying we don't want to help you fix them - sometimes I can't see my own errors because I read what I meant to write - but fixing syntax errors is part of the job, and if you can't do it for yourself people are going to look at you as a bit weird should you get a job in the industry!