Do you really need pseudo code? If yes, then just search and replace some stuff so it's not valid Java anymore. But in general just keep your Java code.

The pseudocode is not a specific language. It is rather pattern of design of some part of code avoiding its syntax when you

• Don't know the language
• Have a better things to do than care about syntax

The example can be - if you want to tell someone how to make a method to check how many array elements are odd you can write

 for every element in the array:
      if is odd:
          increase odd_counter
      else
          do nothing

 print odd_counter

it is not any language it is just "how to write it less or more"

---

Just to make it more visible - please look at tcooc's comment below - the valid code in Java/C++/etc can also be kind of pseudocode

Hi Shekhar, First I would like to explain you what is Pseudo code. Pseudo Code: Pseudo code is a notation which is used to express the intention of your program. While writing Pseudo code, we do not care about syntax. What is important for us is to carry out the intention of the program. Example of ATM withdraw transaction pseudo code: Check the available balance in user's account. if the selected account's balance is greater than the requested amount reduce balance by requested amount and dispense the cash else display error message saying that no sufficient funds end if Coming back to your question: How to convert Java program into Pseudo code? Ans: Very simple ! Understand your program logic properly What is the user input What needs to be generated as output What are the decision that your program is taking based on user input... etc and list goes on :-) Please let me know in case if you still have any confusion. Thanks, Siva

There is no standard pseudo code format. It's very informal. The point is to show the logical structure of the code clearly without getting bogged down in syntax.

If you've been told to pseudo code for assembly, I'd assume that you'd want to break down the java code into, roughly, what it would look like in 68k assembly. This seems to be what you've started here, but you've made a few mistakes.

First, you mean y >= 100.

Your first two ifs should goto ELSE IF, not END IF.

There is no reason to goto IF. You should only be there once. The conditions are not supposed to be checked more than once, according to the java code. Your goto IF should probably be a goto DONE, because it is only executed if the fist condition was true, and this means no other condition will be evaluated.

You need a label for the else condition. This is what you should be going to if x >= y.

You don't want to backtrack to ELSE IF as you do with goto ELSE IF. You probably meant to goto DONE.

Your final goto DONE is redundant. If you had left it out, it would have gone to DONE anyway, seeing as that is the next instruction.

This is roughly what it should look like (Note that the IF label is never referenced. It is just there for looks.):

IF:
  if x <= y 
    goto ELSEIF
  if y >= 100 
    goto ELSEIF
  x++
  y--
  goto DONE
ELSEIF:
  if x >= y 
    goto ELSE
  x--
  y++
  goto DONE
ELSE:
  x = 0
  y = 0
DONE: