Stacks. 2 What is a stack? A stack is a Last In, First Out (LIFO) data structure Anything added to the stack goes on the “top” of the stack Anything removed.

Slides:



Advertisements
Similar presentations
Stacks & Their Applications COP Stacks  A stack is a data structure that stores information arranged like a stack.  We have seen stacks before.
Advertisements

Stacks Chapter 11.
Stacks - 3 Nour El-Kadri CSI Evaluating arithmetic expressions Stack-based algorithms are used for syntactical analysis (parsing). For example.
C o n f i d e n t i a l Developed By Nitendra NextHome Subject Name: Data Structure Using C Title : Overview of Stack.
Stacks, Queues, and Deques. 2 A stack is a last in, first out (LIFO) data structure Items are removed from a stack in the reverse order from the way they.
Stacks CS 3358 – Data Structures. What is a stack? It is an ordered group of homogeneous items of elements. Elements are added to and removed from the.
Topic 15 Implementing and Using Stacks
Stacks.
Infix to postfix conversion Process the tokens from a vector infixVect of tokens (strings) of an infix expression one by one When the token is an operand.
Infix, Postfix, Prefix.
Fall 2007CS 2251 Stacks Chapter 5. Fall 2007CS 2252 Chapter Objectives To learn about the stack data type and how to use its four methods: push, pop,
Stacks. 2 What is a stack? A stack is a Last In, First Out (LIFO) data structure Anything added to the stack goes on the “top” of the stack Anything removed.
Stacks (Revised and expanded from CIT 591). What is a stack? A stack is a Last In, First Out (LIFO) data structure Anything added to the stack goes on.
ECE122 L3: Expression Evaluation February 6, 2007 ECE 122 Engineering Problem Solving with Java Lecture 3 Expression Evaluation and Program Interaction.
Stacks. What is a stack? A stack is a Last In, First Out (LIFO) data structure Anything added to the stack goes on the “top” of the stack Anything removed.
30-Jun-15 Stacks. What is a stack? A stack is a Last In, First Out (LIFO) data structure Anything added to the stack goes on the “top” of the stack Anything.
Topic 15 Implementing and Using Stacks
Stacks, Queues, and Deques
Stacks, Queues, and Deques. A stack is a last in, first out (LIFO) data structure –Items are removed from a stack in the reverse order from the way they.
Stacks, Queues, and Deques
The Stack and Queue Types Lecture 10 Hartmut Kaiser
Expressions, Data Conversion, and Input
Topic 3 The Stack ADT.
Fundamentals of Python: From First Programs Through Data Structures Chapter 14 Linear Collections: Stacks.
1 CSC 222: Computer Programming II Spring 2005 Stacks and recursion  stack ADT  push, pop, peek, empty, size  ArrayList-based implementation, java.util.Stack.
Stack Applications.
1 Stacks Chapter 4 2 Introduction Consider a program to model a switching yard –Has main line and siding –Cars may be shunted, removed at any time.
CSC 205 Programming II Postfix Expressions. Recap: Stack Stack features Orderly linear structure Access from one side only – top item Stack operations.
CHAPTER 05 Compiled by: Dr. Mohammad Omar Alhawarat Stacks & Queues.
Mastering STACKS AN INTRODUCTION TO STACKS Data Structures.
Computer Science Department Data Structure & Algorithms Problem Solving with Stack.
COP3530 Data Structures600 Stack Stack is one the most useful ADTs. Like list, it is a collection of data items. Supports “LIFO” (Last In First Out) discipline.
Stacks  Introduction  Applications  Implementations  Complex Applications.
Recursion. What is recursion? Rules of recursion Mathematical induction The Fibonacci sequence Summary Outline.
A grammar for arithmetic expressions involving the four basic operators and parenthesized expressions. Parenthesized expressions have the highest precedence.
CMP-MX21: Lecture 4 Selections Steve Hordley. Overview 1. The if-else selection in JAVA 2. More useful JAVA operators 4. Other selection constructs in.
For more notes and topics VISIT: IMPLEMENTATION OF STACKS eITnotes.com.
C++ Programming: Program Design Including Data Structures, Fourth Edition Chapter 18: Stacks and Queues (part 2)
Data Structures & Algorithms
CHP-3 STACKS.
Winter 2006CISC121 - Prof. McLeod1 Stuff No stuff today!
1 CSC 222: Computer Programming II Spring 2004 Stacks and recursion  stack ADT  push, pop, top, empty, size  vector-based implementation, library 
CSC 205 – Java Programming II Lecture 30 April 3, 2002.
Stacks A stack is a linear data structure that can be accessed only at one of its ends for storing and retrieving data LIFO (Last In First Out) structure.
CSCI 1100/1202 January 18, Arithmetic Expressions An expression is a combination of operators and operands Arithmetic expressions compute numeric.
Click to edit Master text styles Stacks Data Structure.
Lecture - 6(Stacks) On Data structures. Prepared by, Jesmin Akhter, Lecturer, IIT,JU Lecture Outline What is a Stack? Array implementation of stacks Operations.
CE 221 Data Structures and Algorithms Chapter 3: Lists, Stacks, and Queues - II Text: Read Weiss, §3.6 1Izmir University of Economics.
Chapter 4 Stacks
Stacks Access is allowed only at one point of the structure, normally termed the top of the stack access to the most recently added item only Operations.
CS Data Structures Chapter 6 Stacks Mehmet H Gunes
Revised based on textbook author’s notes.
Multiple variables can be created in one declaration
The Stack ADT. 3-2 Objectives Define a stack collection Use a stack to solve a problem Examine an array implementation of a stack.
Stacks Chapter 4.
COMPUTER 2430 Object Oriented Programming and Data Structures I
Stacks, Queues, and Deques
CSC 205 – Java Programming II
Stacks Chapter 5 Adapted from Pearson Education, Inc.
Stacks.
Stacks, Queues, and Deques
COMPUTER 2430 Object Oriented Programming and Data Structures I
Stacks.
Topic 15 Implementing and Using Stacks
Stacks Chapter 5.
Stack.
Stacks, Queues, and Deques
Stacks.
Chapter 7 (continued) © 2011 Pearson Addison-Wesley. All rights reserved.
Presentation transcript:

Stacks

2 What is a stack? A stack is a Last In, First Out (LIFO) data structure Anything added to the stack goes on the “top” of the stack Anything removed from the stack is taken from the “top” of the stack Things are removed in the reverse order from that in which they were inserted

3 Constructing a stack To use stacks, you need import java.util.*; There is just one stack constructor: Stack stack = new Stack();

4 Stack operations I stack.push(object) Adds the object to the top of the stack; the item pushed is also returned as the value of push object = stack.pop(); Removes the object at the top of the stack and returns it object = stack.peek(); Returns the top object of the stack but does not remove it from the stack

5 Stack operations II stack.empty() Returns true if there is nothing in the stack int i = stack.search(object); Returns the 1-based position of the element on the stack. That is, the top element is at position 1, the next element is at position 2, and so on. Returns -1 if the element is not on the stack

6 Stack ancestry The Stack class extends the Vector class Hence, anything you can do with a Vector, you can also do with a Stack However, this is not how stacks are intended to be used A “stack” is a very specific data structure, defined by the preceding operations; it just happens to be implemented by extending Vector Use only the stack operations for Stack s! The Vector class implements the Collection interface Hence, anything you can do with a Collection, you can also do with a Stack The most useful operation this gives you is toArray()

7 Some uses of stacks Stacks are used for: Any sort of nesting (such as parentheses) Evaluating arithmetic expressions (and other sorts of expression) Implementing function or method calls Keeping track of previous choices (as in backtracking) Keeping track of choices yet to be made (as in creating a maze)

8 A balancing act ([]({()}[()])) is balanced; ([]({()}[())]) is not Simple counting is not enough to check balance You can do it with a stack: going left to right, If you see a (, [, or {, push it on the stack If you see a ), ], or }, pop the stack and check whether you got the corresponding (, [, or { When you reach the end, check that the stack is empty

9 Expression evaluation Almost all higher-level languages let you evaluate expressions, such as 3*x+y or m=m+1 The simplest case of an expression is one number (such as 3 ) or one variable name (such as x ) These are expressions In many languages, = is considered to be an operator Its value is (typically) the value of the left-hand side, after the assignment has occurred Situations sometimes arise where you want to evaluate expressions yourself, without benefit of a compiler

10 Performing calculations To evaluate an expression, such as 1+2*3+4, you need two stacks: one for operands (numbers), the other for operators: going left to right, If you see a number, push it on the number stack If you see an operator, While the top of the operator stack holds an operator of equal or higher precedence: pop the old operator pop the top two values from the number stack and apply the old operator to them push the result on the number stack push the new operator on the operator stack At the end, perform any remaining operations

11 Example: 1+2*3+4 1 : push 1 on number stack + : push + on op stack 2 : push 2 on number stack * : because * has higher precedence than +, push * onto op stack 3 : push 3 onto number stack + : because + has lower precedence than * : pop 3, 2, and * compute 2*3=6, and push 6 onto number stack push + onto op stack 4 : push 4 onto number stack end : pop 4, 6 and +, compute 6+4=10, push 10 ; pop 10, 1, and +, compute 1+10=11, push (at the top of the stack) is the answer

12 Handling parentheses When you see a left parenthesis, (, treat it as a low- priority operator, and just put it on the operator stack When you see a right parenthesis, ), perform all the operations on the operator stack until you reach the corresponding left parenthesis; then remove the left parenthesis

13 Handling variables There are two ways to handle variables in an expression: When you encounter the variable, look up its value, and put its value on the operand (number) stack This simplifies working with the stack, since everything on it is a number When you encounter a variable, put the variable itself on the stack; only look up its value later, when you need it This allows you to have embedded assignments, such as 12 + (x = 5) * x

14 Handling the = operator The assignment operator is just another operator It has a lower precedence than the arithmetic operators It should have a higher precedence than ( To evaluate the = operator: Evaluate the right-hand side (this will already have been done, if = has a low precedence) Store the value of the right-hand side into the variable on the left-hand side You can only do this if your stack contains variables as well as numbers Push the value onto the stack

15 At the end Two things result in multiple special cases You frequently need to compare the priority of the current operator with the priority of the operator at the top of the stack—but the stack may be empty Earlier, I said: “At the end, perform any remaining operations” There is a simple way to avoid these special cases Invent a new “operator,” say, $, and push it on the stack initially Give this operator the lowest possible priority To “apply” this operator, just quit—you’re done

16 Some things that can go wrong The expression may be ill-formed: When you go to evaluate the second +, there won’t be two numbers on the stack When you are done evaluating the expression, you have more than one number on the stack (2 + 3 You have an unmatched ( on the stack 2 + 3) You can’t find a matching ( on the stack The expression may use a variable that has not been assigned a value

17 Types of storage In almost all languages (including Java), data is stored in two different ways: Temporary variables—parameters and local variables of a method—are stored in a stack These values are popped off the stack when the method returns The value returned from a method is also temporary, and is put on the stack when the method returns, and removed again by the calling program More permanent variables—objects and their instance variables and class variables—are kept in a heap They remain on the heap until they are “freed” by the programmer (C, C++) or garbage collected (Java)

18 Stacks in Java Stacks are used for local variables (including parameters) void methodA() { int x, y; // puts x, y on stack y = 0; methodB(); y++; } void methodB() { int y, z; // puts y, z on stack y = 5; return; // removes y, z } x y y z

19 Supporting recursion static int factorial(int n) { if (n <= 1) return 1; else return n * factorial(n - 1); } If you call x = factorial(3), this enters the factorial method with n=3 on the stack | factorial calls itself, putting n=2 on the stack | | factorial calls itself, putting n=1 on the stack | | factorial returns 1 | factorial has n=2, computes and returns 2*1 = 2 factorial has n=3, computes and returns 3*2 = 6

20 Factorial (animation 1) x = factorial(3) static int factorial(int n) { //n=3 int r = 1; if (n <= 1) return r; else { r = n * factorial(n - 1); return r; } } n=3 r=1 r is put on stack with value 1 All references to r use this r All references to n use this n 3 is put on stack as n Now we recur with 2...

21 Factorial (animation 2) r = n * factorial(n - 1); static int factorial(int n) {//n=2 int r = 1; if (n <= 1) return r; else { r = n * factorial(n - 1); return r; } } n=3 r=1 r is put on stack with value 1 Now using this r And this n Now we recur with 1... n=2 r=1 2 is put on stack as n

22 Factorial (animation 3) r = n * factorial(n - 1); static int factorial(int n) { int r = 1; if (n <= 1) return r; else { r = n * factorial(n - 1); return r; } } n=3 r=1 r is put on stack with value 1 Now using this r And this n n=2 r=1 n=1 r=1 1 is put on stack as n Now we pop r and n off the stack and return 1 as factorial(1)

23 n=1 r=1 Factorial (animation 4) r = n * factorial(n - 1); static int factorial(int n) { int r = 1; if (n <= 1) return r; else { r = n * factorial(n - 1); return r; } } n=3 r=1 Now using this r And this n n=2 r=1 n=1 fac=1 Now we pop r and n off the stack and return 1 as factorial(1)

24 Factorial (animation 5) r = n * factorial(n - 1); static int factorial(int n) { int r = 1; if (n <= 1) return r; else { r = n * factorial(n - 1); return r; } } n=3 r=1 Now using this r And this n 2 * 1 is 2 ; Pop r and n; Return 2 r=1 n=2 1 fac=2

25 Factorial (animation 6) x = factorial(3) static int factorial(int n) { int r = 1; if (n <= 1) return r; else { r = n * factorial(n - 1); return r; } } n=3 r=1 Now using this r And this n 3 * 2 is 6 ; Pop r and n; Return 6 2 r=1 n=3 fac=6

26 Stack frames Rather than pop variables off the stack one at a time, they are usually organized into stack frames Each frame provides a set of variables and their values This allows variables to be popped off all at once There are several different ways stack frames can be implemented n=3 r=1 n=2 r=1 n=1 r=1

27 Generic Stack s in Java 5 Here’s the old way of using Stack s (which still works, but you may get a warning message): Stack myStack = new Stack(); // possible warning here myStack.push(Color.RED); myStack.push("abcde"); String myString = (String)myStack.pop(); Java 5 prefers, but does not require, that you specify the type of things on the stack: Stack myStack = new Stack (); myStack.push(Color.RED); // now a syntax error! myStack.push("abcde"); String myString = myStack.pop(); // no cast needed!

28 Summary Stacks are useful for working with any nested structure, such as: Arithmetic expressions Nested statements in a programming language Any sort of nested data

29 The End