Operations on stack

Question

Hi guys,
I've got a simple stack working, but am having some problems with the input commands. Basically, the commands "empty", "pop", and "peek" are only meant to operate on the stack, not to be inserted inside it. They function on it and also operate on it. Any suggestions how this can be fixed? I don't want them to be inserted into my stack, just to operate.
Heres my code:
// Code By SSPanesar, 2006
// this code was made using Java API
import java.util.*;
import java.io.*;
public class Stacks2
public Stacks2()
         Stack pile = new Stack(); // making a new instance Stack
        String s = "";
        boolean truth = false;
        int check = 0; // used as a counter
        BufferedReader in = new BufferedReader(new InputStreamReader(System.in));
        System.out.println("Please enter some text, and finish with 'end'");
        while (truth == false)
          try
             s = in.readLine();
          catch(IOException e)
            if(s.equals("end")) // what to enter to end program
                      truth = true;
                if(s.equals("pop"))
                   if(check==1)
                     System.out.println("stack empty");
                     // truth = true; THIS IS INSERTED HERE TO END THE PROGRAM WHEN THE STACK IS EMPTY (OPTIONAL)
                   else
                         check = check - 1;
                         System.out.println("The value: "+pile.pop()+" has been removed from the stack");
                         System.out.println("The size of the Stack is: "+check);
            if(s.equals("peek")) // reading top value of the program
                    System.out.println("The top value in the stack is: "+pile.peek());
          else
            pile.push(s);
            check = check + 1;
            System.out.println("You Just entered into the Stack :"+s);
          for(int a=0;a<check;a++)
            System.out.println(pile.pop());
        public static void main(String[] args)
           Stacks2 box = new Stacks2();
}

Answer 1

ok, so with the code that I have here, is there no
alteration that can be done to solve this problem?First, you haven't really defined what the problem is, aside from saying that you don't want to define methods like pop() and push() in your Stack class. That doesn't make any sense, and I've pointed you to some resources that tell you why.
Second, I haven't bothered to dissect your code because it's a bit tough to look at. I recommend that for now, you strictly adhere to the standard Code Conventions for the Java� Programming Language. It will make your code much easier to read, which of course, makes it much more likely you'll get others to look at it.
Third, don't flag your question as urgent, even if it is for you.
* We all answer questions here voluntarily, in our leisure time. We do that because doing so is fun for us, because we enjoy helping people and having interesting discussions. Guess what, it is much less fun if it gets stressful. So the last thing you want to do to get us to answer your question is to pass your stress over to us.
* People who are stressed and want a fast answer often don't even find the time to do the necessary research or to formulate their question in an easy to comprehend way. That's even less fun to work with. So you really don't want us to feel your stress. Instead you want to take your time to write a well formulated post that is fun to answer. The less likely it is for us to know that your question is urgent, the more likely you are to get a fast answer!
* The simple notion that you want your post to be answered faster than those of the other members might feel rather unfair to some of us. Doubly so because often "urgent" questions actually are homework questions. Yours might be different, but someone who had bad experiences with this type of question might not read far enough to notice.
So, yes, there is alteration that can (and should be done). Read those links, and research existing example Stack code. There are scads of examples out on the web, and will be easy to find. If you have a specific coding error that you're having trouble working out, make sure you describe the problem specifically.
Good luck!