Click here to Skip to main content
15,617,020 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
i tried to create the method and also the array for the attempt of the user input but it didn't print the answer.

What I have tried:

<pre>import java.util.Scanner;
 * @author User
public class Intermediate {
    public static void main(String[]args){
        int numAttempt;
        numAttempt = enterNumAttempt();
        marks = new int[numAttempt];
    public static void greetings(){
        System.out.print("Grading Method: Highest Grade !!!");
    public static int enterNumAttempt(){
        Scanner scan = new Scanner (;
        System.out.println("How many attempts that you tried:  ");
        int n= scan.nextInt();
        int[]arr = new int[n];
        return 0;
     public static void enterMarks(int[] marks, int[] arr){
        Scanner scan = new Scanner (;
        System.out.println("Enter your marks: ");
        int[] n = null;
        for(marks = 0; marks<n; marks++){
            arr[marks] = scan.nextInt();
            System.out.println(" ");
    public static void determineGrade(int[] arr){
        int max = 0;
        int n = 0;
        for(int marks=0; marks<n;marks++){
        if (arr[marks]> max)
            max= arr[marks];
Updated 28-Jan-23 8:47am

Compiling does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.

So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.

Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:
Input   Expected output    Actual output
  1            2                 1
  2            4                 4
  3            6                 9
  4            8                16
Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:
private int Double(int value)
   return value * value;

Once you have an idea what might be going wrong, start using the debugger to find out why. Put a breakpoint on the first line of the method, and run your app. When it reaches the breakpoint, the debugger will stop, and hand control over to you. You can now run your code line-by-line (called "single stepping") and look at (or even change) variable contents as necessary (heck, you can even change the code and try again if you need to).
Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?
Hopefully, that should help you locate which part of that code has a problem, and what the problem is.
This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!
Share this answer
Even before you get to what OriginalGriff stated in his solution you will need to fix some compilation errors. The program won't even run let alone print your desired result. The code almost looks like a little panic has set in causing a bit of flailing about. Not to worry. You're actually not that far off from a working solution. It probably just seems worse than it is.

So, first thing - fix the compilation errors. I see 6 of them. Your compiler should tell you the line and column at which each error occurs. Read the error message. It actually tells you what is wrong but for the the new programmer the wording can be confusing sometimes. Just look at the line it's complaining about. For example, the first error shows a problem with calling enterMarks. Look at how you call it, then look at how it's defined. Think about how it should be called and defined and make the changes so both match up.

Once you have the compilation errors resolved then it's time to take OriginalGriff's advice. Run the code in the debugger and start comparing what happens to what you expect.
Share this answer

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

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900