Click here to Skip to main content
15,886,069 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
About below coding, when I put 'System.out.println(i)'
inside {} after 'for(int i=1;i<=20;i++){', it printed out #1-20.

Why 'System.out.println(i)' should be placed after 'if(i%3==0){continue; }'?

public static void main(String[] args) {
	 
 for(int i=1;i<=20;i++) {
	
	 if(i %3==0) {
			continue;
		}
	 System.out.println(i);
 }
	}	


What I have tried:

Result of below coding is #1-20.

public static void main(String[] args) {
    
 for(int i=1;i<=20;i++) {
	 System.out.println(i);
	 if(i %3==0) {
			continue;
		}
	
 }
	}	
Posted
Updated 5-Mar-21 11:47am
Comments
Afzaal Ahmad Zeeshan 5-Mar-21 17:31pm    
What else did you expect this code to show?

continue is a loop construct in many languages, and it always means the same thing: "ignore the rest of the loop body and go round the next iteration, if any".
So once the continue statement has been executed, no more code in the loop body will be, this time round, execution will "skip" back to the nearest loop

In the case of your for loop, the next code executed executed after a continue will be the incrementor code: i++, followed by the termination test.

In your second example, the continue is the last statement in the loop body, so it effectively does nothing, as there is no loop body code to "skip" if it is executed!
 
Share this answer
 
Comments
lem0n2222 5-Mar-21 20:07pm    
Thank you so much! I understood!
OriginalGriff 6-Mar-21 2:11am    
You're welcome!
Your code do not behave the way you expect, or you don't understand why !

There is an almost universal solution: Run your code on debugger step by step, inspect variables.
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't know what your code is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
To see what your code is doing: Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.

Debugger - Wikipedia, the free encyclopedia[^]

Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[^]
Basic Debugging with Visual Studio 2010 - YouTube[^]

27.3. pdb — The Python Debugger — Python 3.6.1 documentation[^]
Debugging in Python | Python Conquers The Universe[^]
pdb – Interactive Debugger - Python Module of the Week[^]

The debugger is here to only show you what your code is doing and your task is to compare with what it should do.
 
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