We use cookies to ensure you have the best browsing experience on our website. Please read our cookie policy for more information about how we use cookies.
Loading...
  1. Practice
  2. Data Structures
  3. Stacks
  4. Simple Text Editor
  5. Discussions

Simple Text Editor

  • mk9440 + 4 comments

    Simple java Solution : - :D

    public class Solution {
 public static void main(String[] args) {
       Scanner in=new Scanner(System.in);
       int n=in.nextInt();
       String s = "";
      Stack<String> st =new Stack<String>();
      st.push(s);
        for(int i=0;i<n;i++){
        	 int t=in.nextInt();
            if(t==1){ s = s+in.next();st.push(s);
               }
            else if(t==2){s=s.substring(0,s.length()-in.nextInt());st.push(s);}
            else if(t==3){System.out.println(s.charAt(in.nextInt()-1)); }
            else{st.pop();s=st.peek();}}}}
    • Dipak_Prajapati + 1 comment

      thanks man, you solve my problem.

      • mk9440 + 0 comments

        Glad , it Helped :D

    • miguelblcfiguei1 + 0 comments

      nice! But to be even simpler I would have written it with a switch instead of many "else if"s

    • Kill_Switch + 1 comment

      Can u just explain what this is doing? else{st.pop();s=st.peek();}}}

      • mk9440 + 1 comment

        In this problem,by using stack,the basic idea is to store each modified string after the append or delete operation performed on them. Now the fourth option is to undo last step on string and as the previous modified(last modified) string must be on the top of stack so here we have to pop it(st.pop()).After poping,the top of stack will now point that string which it was before performing the last modification operation (append or delete) on it and we will now store its present top element in s ie s=st.peek()

        • abirb + 0 comments

          Thank you so much.

    • tarabahadur_tha1 + 1 comment

      wouldn't it be better to use StringBuffer ?

      • mk9440 + 2 comments

        Yes it would have been memory efficient and less time consuming but as this passes all test cases so have not made other effort, but it should be good programming practise to use StringBuffer instead. :)

        • register9091 + 0 comments

          String buffer seems to be leading to timeout. String works better.

        • kevinersoy + 0 comments

          This times out on 4 or 5 test cases