Chapter 4 Linked Structures - Stacks

Slides:



Advertisements
Similar presentations
Chapter 17 Recursion.
Advertisements

© 2010 Pearson Addison-Wesley. All rights reserved. Addison Wesley is an imprint of CHAPTER 7: Recursion Java Software Structures: Designing and Using.
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.
Elementary Data Structures CS 110: Data Structures and Algorithms First Semester,
Chapter 5 Queues Modified. Chapter Scope Queue processing Comparing queue implementations 5 - 2Java Software Structures, 4th Edition, Lewis/Chase.
Chapter 6 Linked Structures © 2006 Pearson Education Inc., Upper Saddle River, NJ. All rights reserved.
Chapter 7 Iterators Modified. Chapter Scope The purpose of an iterator The Iterator and Interable interfaces The concept of fail-fast collections Using.
Unit 11 1 Unit 11: Data Structures H We explore some simple techniques for organizing and managing information H This unit focuses on: Abstract Data Types.
CHAPTER 6 Stacks Array Implementation. 2 Stacks A stack is a linear collection whose elements are added and removed from one end The last element to be.
Chapter 6 Stacks. Copyright © 2005 Pearson Addison-Wesley. All rights reserved. 6-2 Chapter Objectives Examine stack processing Define a stack abstract.
Chapter 13 Linked Structures - Stacks. Chapter Scope Object references as links Linked vs. array-based structures Managing linked lists Linked implementation.
Stacks, Queues, and Deques
Chapter 14 Queues. First a Review Queue processing Using queues to solve problems – Optimizing customer service simulation – Ceasar ciphers – Palindrome.
Chapter 4 Linked Structures – Stacks Modified. Chapter Scope Object references as links Linked vs. array-based structures Managing linked lists Linked.
Chapter 12 Introduction to Collections - Stacks
1 CMPSCI 187 Computer Science 187 Introduction to Introduction to Programming with Data Structures Lecture 11: Stacks and Mazes Announcements 1.Midterm.
Abstract Data Types (ADTs) and data structures: terminology and definitions A type is a collection of values. For example, the boolean type consists of.
Topic 3 The Stack ADT.
Chapter 3 Introduction to Collections – Stacks Modified
Chapter 8 Lists. Copyright © 2004 Pearson Addison-Wesley. All rights reserved.1-2 Chapter Objectives Examine list processing and various ordering techniques.
Chapter 7 Arrays. © 2004 Pearson Addison-Wesley. All rights reserved11-2 Arrays Arrays are objects that help us organize large amounts of information.
Chapter 6 Stacks. Copyright © 2004 Pearson Addison-Wesley. All rights reserved.1-2 Chapter Objectives Examine stack processing Define a stack abstract.
1 Linked-list, stack and queue. 2 Outline Abstract Data Type (ADT)‏ Linked list Stack Queue.
Linked Structures - Review Chapter 13 Instructor: Scott Kristjanson CMPT 125/125 SFU Burnaby, Fall 2013.
1 Recursion Recursion is a powerful programming technique that provides elegant solutions to certain problems. Chapter 11 focuses on explaining the underlying.
Linked Structures, LinkedStack
COS 312 DAY 19 Tony Gauvin. Ch 1 -2 Agenda Questions? Capstone Progress reports over due Assignment 6 Posted – Due April 16 Layers using non-opaque panels.
1 Stacks (Continued) and Queues Array Stack Implementation Linked Stack Implementation The java.util.Stack class Queue Abstract Data Type (ADT) Queue ADT.
© 2010 Pearson Addison-Wesley. All rights reserved. Addison Wesley is an imprint of CHAPTER 15: Sets and Maps Java Software Structures: Designing and Using.
TOWERS OF HANOI. : If n = 1, move disk 1 from pole 'A' to pole 'B'. else: 1.First, move n-1 disks from pole 'A' to pole 'C', using pole 'B' as.
COS 312 DAY 18 Tony Gauvin. Ch 1 -2 Agenda Questions? Capstone Progress reports over due Assignment 5 Corrected – 1 A, 2 B’s, 1 C, 1 D 1 F and 1 MIA –
Linked Structures Chapter 13 Instructor: Scott Kristjanson CMPT 125/125 SFU Burnaby, Fall 2013.
COS 312 DAY 23 Tony Gauvin. Ch 1 -2 Agenda Questions? Capstone progress report Overdue Assignment 6 Over Due Assignment 7 (bonus) – Due May 11 – Will.
Collections & Stacks Collections A collection is an object that holds and organizes other objects It provides operations for accessing and managing.
COS 312 DAY 24 Tony Gauvin. Ch 1 -2 Agenda Questions? Assignment 6 Corrected Assignment 7 (bonus) – Due May 11 – Will be scored on 15 point scale, points.
Iterators. Chapter Scope The purpose of an iterator The Iterator and Interable interfaces The concept of fail-fast collections Using iterators to solve.
Linked Structures - Stacks. Linked Structures An alternative to array-based implementations are linked structures A linked structure uses object references.
COS 312 DAY 20 Tony Gauvin. Ch 1 -2 Agenda Questions? Next Capstone progress report is due April 25 Assignment 5 Graded – Not much original code Assignment.
Java Software Solutions Foundations of Program Design Seventh Edition
Section 3.7 Linked-Based Implementations
Stack: a Linked Implementation
Elementary Data Structures
CHAPTER 4: Linked Structures
The List ADT.
Chapter 4 Linked Structures.
Storage Strategies: Dynamic Linking
Chapter 12: Data Structures
Stacks.
Chapter 14: Stacks.
Stacks and Queues.
The Stack ADT. 3-2 Objectives Define a stack collection Use a stack to solve a problem Examine an array implementation of a stack.
Stack and Queue APURBO DATTA.
Java Software Structures: John Lewis & Joseph Chase
Chapter 3 Introduction to Collections - Stacks
Top Ten Words that Almost Rhyme with “Peas”
Chapter 5 Queues.
CMSC 341 Lecture 5 Stacks, Queues
Chapter 7 Iterators.
Java Software Structures: John Lewis & Joseph Chase
Chapter 12 Recursion (methods calling themselves)
Chapter 4 Linked Structures - Stacks
Chapter 13 Collections.
Stacks, Queues, and Deques
Java Software Structures: John Lewis & Joseph Chase
Chapter 8 Recursion.
Stacks, Queues, and Deques
A type is a collection of values
CHAPTER 3: Collections—Stacks
Presentation transcript:

Chapter 4 Linked Structures - Stacks

Chapter Scope Object references used as links Linked vs. array-based structures Managing linked lists Linked implementation of a stack Java Software Structures, 4th Edition, Lewis/Chase

Linked Structures An alternative to array-based implementations are linked structures A linked structure uses object references to create links between objects Recall that an object reference variable holds the address of an object Java Software Structures, 4th Edition, Lewis/Chase

Linked Structures A Person object, for instance, could contain a reference to another Person object A series of Person objects would make up a linked list: Java Software Structures, 4th Edition, Lewis/Chase

Linked Structures Links could also be used to form more complicated, non-linear structures Java Software Structures, 4th Edition, Lewis/Chase

Linked Lists There are no index values built into linked lists To access each node in the list you must follow the references from one node to the next Person current = first; while (current != null) { System.out.println(current); current = current.next; } Java Software Structures, 4th Edition, Lewis/Chase

Linked Lists Care must be taken to maintain the integrity of the links To insert a node at the front of the list, first point the new node to the front node, then reassign the front reference Java Software Structures, 4th Edition, Lewis/Chase

Linked Lists To delete the first node, reassign the front reference accordingly If the deleted node is needed elsewhere, a reference to it must be established before reassigning the front pointer Java Software Structures, 4th Edition, Lewis/Chase

Linked Lists So far we've assumed that the list contains nodes that are self-referential (Person points to a Person) But often we'll want to make lists of objects (String objects for examples) that don't contain such references Solution: have a separate Node class that forms the list and holds a reference to the objects (elements) being stored Java Software Structures, 4th Edition, Lewis/Chase

Linked Lists There are many variations on the basic linked list concept For example, we could create a doubly-linked list with next and previous references in each node and a separate pointer to the rear of the list Java Software Structures, 4th Edition, Lewis/Chase

Stacks Revisited In the previous chapter we developed our own array-based version of a stack, and we also used the java.util.Stack class from the Java API The API's stack class is derived from Vector, which has many non-stack abilities It is, therefore, not the best example of inheritance, because a stack is not a vector It's up to the user to use a Stack object only as intended Java Software Structures, 4th Edition, Lewis/Chase

Stacks Revisited Stack characteristics can also be found by using the Deque interface from the API The LinkedList class implements the Deque interface Deque stands for double-ended queue, and will be explored further later For now, we will use the stack characteristics of a Deque to solve the problem of traversing a maze Java Software Structures, 4th Edition, Lewis/Chase

Using Stacks: Traversing a Maze Suppose a two-dimensional maze is represented as a grid of 1 (path) and 0 (wall) Goal: traverse from the upper left corner to the bottom right (no diagonal moves) 9 13 1 1 1 0 1 1 0 0 0 1 1 1 1 1 0 0 1 1 0 1 1 1 1 0 0 1 1 1 1 1 1 0 1 0 1 0 1 0 0 0 0 0 0 1 1 1 0 1 0 1 1 1 1 1 1 0 1 1 1 0 1 0 1 1 1 1 0 1 0 0 0 0 1 1 1 0 0 1 1 0 1 1 1 1 1 1 0 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 Java Software Structures, 4th Edition, Lewis/Chase

Traversing a Maze Using a stack, we can perform a backtracking algorithm to find a solution to the maze An object representing a position in the maze is pushed onto the stack when trying a path If a dead end is encountered, the position is popped and another path is tried We'll change the integers in the maze grid to represent tried-but-failed paths (2) and the successful path (3) Java Software Structures, 4th Edition, Lewis/Chase

import java. util. ; import java. io. ; / import java.util.*; import java.io.*; /** * Maze represents a maze of characters. The goal is to get from the * top left corner to the bottom right, following a path of 1's. Arbitrary * constants are used to represent locations in the maze that have been TRIED * and that are part of the solution PATH. * * @author Lewis and Chase * @version 4.0 */ public class Maze { private static final int TRIED = 2; private static final int PATH = 3; private int numberRows, numberColumns; private int[][] grid; Java Software Structures, 4th Edition, Lewis/Chase

/. Constructor for the Maze class. Loads a maze from the given file /** * Constructor for the Maze class. Loads a maze from the given file. * Throws a FileNotFoundException if the given file is not found. * * @param filename the name of the file to load * @throws FileNotFoundException if the given file is not found */ public Maze(String filename) throws FileNotFoundException { Scanner scan = new Scanner(new File(filename)); numberRows = scan.nextInt(); numberColumns = scan.nextInt(); grid = new int[numberRows][numberColumns]; for (int i = 0; i < numberRows; i++) for (int j = 0; j < numberColumns; j++) grid[i][j] = scan.nextInt(); } Java Software Structures, 4th Edition, Lewis/Chase

/. Marks the specified position in the maze as TRIED /** * Marks the specified position in the maze as TRIED * * @param row the index of the row to try * @param col the index of the column to try */ public void tryPosition(int row, int col) { grid[row][col] = TRIED; } * Return the number of rows in this maze * @return the number of rows in this maze public int getRows() return grid.length; * Return the number of columns in this maze * @return the number of columns in this maze public int getColumns() return grid[0].length; Java Software Structures, 4th Edition, Lewis/Chase

Java Software Structures, 4th Edition, Lewis/Chase /** * Marks a given position in the maze as part of the PATH * * @param row the index of the row to mark as part of the PATH * @param col the index of the column to mark as part of the PATH */ public void markPath(int row, int col) { grid[row][col] = PATH; } * Determines if a specific location is valid. A valid location * is one that is on the grid, is not blocked, and has not been TRIED. * @param row the row to be checked * @param column the column to be checked * @return true if the location is valid public boolean validPosition(int row, int column) boolean result = false; // check if cell is in the bounds of the matrix if (row >= 0 && row < grid.length && column >= 0 && column < grid[row].length) // check if cell is not blocked and not previously tried if (grid[row][column] == 1) result = true; return result; Java Software Structures, 4th Edition, Lewis/Chase

Java Software Structures, 4th Edition, Lewis/Chase /** * Returns the maze as a string. * * @return a string representation of the maze */ public String toString() { String result = "\n"; for (int row=0; row < grid.length; row++) for (int column=0; column < grid[row].length; column++) result += grid[row][column] + ""; result += "\n"; } return result; Java Software Structures, 4th Edition, Lewis/Chase

Java Software Structures, 4th Edition, Lewis/Chase import java.util.*; /** * MazeSolver attempts to traverse a Maze using a stack. The goal is to get from the * given starting position to the bottom right, following a path of 1's. Arbitrary * constants are used to represent locations in the maze that have been TRIED * and that are part of the solution PATH. * * @author Lewis and Chase * @version 4.0 */ public class MazeSolver { private Maze maze; * Constructor for the MazeSolver class. public MazeSolver(Maze maze) this.maze = maze; } Java Software Structures, 4th Edition, Lewis/Chase

Java Software Structures, 4th Edition, Lewis/Chase /** * Attempts to traverse the maze using a stack. Inserts special * characters indicating locations that have been TRIED and that * eventually become part of the solution PATH. * * @param row row index of current location * @param column column index of current location * @return true if the maze has been solved */ public boolean traverse() { boolean done = false; int row, column; Position pos = new Position(); Deque<Position> stack = new LinkedList<Position>(); stack.push(pos); while (!(done) && !stack.isEmpty()) pos = stack.pop(); maze.tryPosition(pos.getx(),pos.gety()); // this cell has been tried if (pos.getx() == maze.getRows()-1 && pos.gety() == maze.getColumns()-1) done = true; // the maze is solved else push_new_pos(pos.getx() - 1,pos.gety(), stack); push_new_pos(pos.getx() + 1,pos.gety(), stack); push_new_pos(pos.getx(),pos.gety() - 1, stack); push_new_pos(pos.getx(),pos.gety() + 1, stack); } return done; Java Software Structures, 4th Edition, Lewis/Chase

Java Software Structures, 4th Edition, Lewis/Chase /** * Push a new attempted move onto the stack * @param x represents x coordinate * @param y represents y coordinate * @param stack the working stack of moves within the grid * @return stack of moves within the grid */ private void push_new_pos(int x, int y, Deque<Position> stack) { Position npos = new Position(); npos.setx(x); npos.sety(y); if (maze.validPosition(x,y)) stack.push(npos); } Java Software Structures, 4th Edition, Lewis/Chase

Java Software Structures, 4th Edition, Lewis/Chase import java.util.*; import java.io.*; /** * MazeTester determines if a maze can be traversed. * * @author Lewis and Chase * @version 4.0 */ public class MazeTester { * Creates a new maze, prints its original form, attempts to * solve it, and prints out its final form. public static void main(String[] args) throws FileNotFoundException Scanner scan = new Scanner(System.in); System.out.print("Enter the name of the file containing the maze: "); String filename = scan.nextLine(); Maze labyrinth = new Maze(filename); System.out.println(labyrinth); MazeSolver solver = new MazeSolver(labyrinth); if (solver.traverse()) System.out.println("The maze was successfully traversed!"); else System.out.println("There is no possible path."); } Java Software Structures, 4th Edition, Lewis/Chase

Implementing a Stack using Links Let's now implement our own version of a stack that uses a linked list to hold the elements Our LinkedStack<T> class stores a generic type T and implements the same StackADT<T> interface used previously A separate LinearNode<T> class forms the list and hold a reference to the element stored An integer count will store how many elements are currently in the stack Java Software Structures, 4th Edition, Lewis/Chase

Implementing a Stack using Links Since all activity on a stack happens on one end, a single reference to the front of the list will represent the top of the stack Java Software Structures, 4th Edition, Lewis/Chase

Implementing a Stack using Links The stack after A, B, C, and D are pushed, in that order: Java Software Structures, 4th Edition, Lewis/Chase

Implementing a Stack using Links After E is pushed onto the stack: Java Software Structures, 4th Edition, Lewis/Chase

Java Software Structures, 4th Edition, Lewis/Chase package jsjf; /** * Represents a node in a linked list. * * @author Lewis and Chase * @version 4.0 */ public class LinearNode<T> { private LinearNode<T> next; private T element; * Creates an empty node. public LinearNode() next = null; element = null; } * Creates a node storing the specified element. * @param elem element to be stored public LinearNode(T elem) element = elem; Java Software Structures, 4th Edition, Lewis/Chase

Java Software Structures, 4th Edition, Lewis/Chase /** * Returns the node that follows this one. * @return reference to next node */ public LinearNode<T> getNext() { return next; } * Sets the node that follows this one. * @param node node to follow this one public void setNext(LinearNode<T> node) next = node; * Returns the element stored in this node. * @return element stored at the node public T getElement() return element; * Sets the element stored in this node. * @param elem element to be stored at this node public void setElement(T elem) element = elem; Java Software Structures, 4th Edition, Lewis/Chase

package jsjf; import jsjf.exceptions.*; import java.util.Iterator; /** * Represents a linked implementation of a stack. * * @author Lewis and Chase * @version 4.0 */ public class LinkedStack<T> implements StackADT<T> { private int count; private LinearNode<T> top; * Creates an empty stack. public LinkedStack() count = 0; top = null; } Java Software Structures, 4th Edition, Lewis/Chase

/. Adds the specified element to the top of this stack /** * Adds the specified element to the top of this stack. * @param element element to be pushed on stack */ public void push(T element) { LinearNode<T> temp = new LinearNode<T>(element); temp.setNext(top); top = temp; count++; } * Removes the element at the top of this stack and returns a * reference to it. * @return element from top of stack * @throws EmptyCollectionException if the stack is empty public T pop() throws EmptyCollectionException if (isEmpty()) throw new EmptyCollectionException("stack"); T result = top.getElement(); top = top.getNext(); count--; return result; Java Software Structures, 4th Edition, Lewis/Chase

Implementing a Stack using Links Java Software Structures, 4th Edition, Lewis/Chase