Stacks and Linked Lists. Abstract Data Types (ADTs) An ADT is an abstraction of a data structure that specifies – Data stored – Operations on the data.

Slides:



Advertisements
Similar presentations
STACKS & QUEUES. Stacks Abstract data types An abstract data type (ADT) is an abstraction of a data structure An ADT specifies : –Data stored –Operations.
Advertisements

Stacks.
Queues and Linked Lists
© 2004 Goodrich, Tamassia Queues1. © 2004 Goodrich, Tamassia Queues2 The Queue ADT (§4.3) The Queue ADT stores arbitrary objects Insertions and deletions.
Chapter 5.
Queues1 Part-B2 Queues. Queues2 The Queue ADT (§4.3) The Queue ADT stores arbitrary objects Insertions and deletions follow the first-in first-out scheme.
Queues 4/14/2017 5:24 PM 5.2 Queues Queues Dr Zeinab Eid.
1 Queues (5.2) CSE 2011 Winter May Announcements York Programming Contest Link also available from.
Stacks. Queues. Double-Ended Queues. 2 CPSC 3200 University of Tennessee at Chattanooga – Summer 2013 © 2010 Goodrich, Tamassia.
Stacks. 2 Outline and Reading The Stack ADT (§4.2.1) Applications of Stacks (§4.2.3) Array-based implementation (§4.2.2) Growable array-based stack.
© 2004 Goodrich, Tamassia Stacks. © 2004 Goodrich, Tamassia Stacks2 The Stack ADT (§4.2) The Stack ADT stores arbitrary objects Insertions and deletions.
© 2004 Goodrich, Tamassia Stacks. © 2004 Goodrich, Tamassia Stacks2 Abstract Data Types (ADTs) An abstract data type (ADT) is an abstraction of a data.
Data Structures Lecture 5 Fang Yu Department of Management Information Systems National Chengchi University Fall 2010.
Queues. What is a queue? First-in first-out data structure (FIFO) New objects are placed at rear Removal restricted to front Examples?
Elementary Data Structures Stacks, Queues, & Lists Amortized analysis Trees.
Stacks. 2 Outline and Reading The Stack ADT (§2.1.1) Array-based implementation (§2.1.1) Growable array-based stack (§1.5) Java.util.Stack class Java.util.Vector.
Part-B1 Stacks. Stacks2 Abstract Data Types (ADTs) An abstract data type (ADT) is an abstraction of a data structure An ADT specifies: Data stored Operations.
Part-B1 Stacks. Stacks2 Abstract Data Types (ADTs) An abstract data type (ADT) is an abstraction of a data structure An ADT specifies: Data stored Operations.
Stacks. 2 Outline and Reading The Stack ADT (§2.1.1) Applications of Stacks (§2.1.1) Array-based implementation (§2.1.1) Growable array-based stack (§1.5)
Implementing and Using Stacks
© 2004 Goodrich, Tamassia Vectors1 Lecture 03 Vectors, Lists and Sequences Topics Vectors Lists Sequences.
Circular queue. Array-based Queue Use an array of size N in a circular fashion Three variables keep track of the front, rear, and size f index of the.
© 2004 Goodrich, Tamassia Queues1. © 2004 Goodrich, Tamassia Queues2 The Queue ADT (§4.3) The Queue ADT stores arbitrary objects Insertions and deletions.
Stacks. week 2a2 Outline and Reading The Stack ADT (§4.1) Applications of Stacks Array-based implementation (§4.1.2) Growable array-based stack Think.
Stacks 1. Stack  What is a stack? An ordered list where insertions and deletions occur at one end called the top. Also known as last-in-first-out (LIFO)
© 2004 Goodrich, Tamassia Stacks. © 2004 Goodrich, Tamassia Stacks2 Abstract Data Types (ADTs) An abstract data type (ADT) is an abstraction of a data.
Stacks. A stack is a data structure that holds a sequence of elements and stores and retrieves items in a last-in first- out manner (LIFO). This means.
30 May Stacks (5.1) CSE 2011 Winter Stacks2 Abstract Data Types (ADTs) An abstract data type (ADT) is an abstraction of a data structure An.
Queues by Dr. Bun Yue Professor of Computer Science CSCI 3333 Data Structures.
STACKS AND QUEUES 1. Outline 2  Stacks  Queues.
Lecture7: Queue Bohyung Han CSE, POSTECH CSED233: Data Structures (2014F)
Dynamic Arrays and Stacks CS 244 Brent M. Dingle, Ph.D. Game Design and Development Program Department of Mathematics, Statistics, and Computer Science.
Lecture6: Stacks Bohyung Han CSE, POSTECH CSED233: Data Structures (2014F)
Lecture 3 Queues Queues1. queue: – Retrieves elements in the order they were added. – First-In, First-Out ("FIFO") – Elements are stored in order of insertion.
© 2004 Goodrich, Tamassia Vectors1 Vectors and Array Lists.
Array Lists1 © 2010 Goodrich, Tamassia. Array Lists2 The Array List ADT  The Array List ADT extends the notion of array by storing a sequence of arbitrary.
Dynamic Arrays and Stacks Data Structures and Algorithms CS 244 Brent M. Dingle, Ph.D. Department of Mathematics, Statistics, and Computer Science University.
Queue. Avoid confusion Britain Italy 6 Applications of Queues Direct applications –Waiting lists, bureaucracy –Access to shared resources (e.g.,
Parasol Lab, Dept. CSE, Texas A&M University
Welcome to CSCE 221 – Data Structures and Algorithms
Queue. The Queue ADT Insertions and deletions follow the first-in first-out scheme Insertions are at the rear of the queue and removals are at the front.
CH 5 : STACKS, QUEUES, AND DEQUES ACKNOWLEDGEMENT: THE SLIDES ARE PREPARED FROM SLIDES PROVIDED WITH DATA STRUCTURES AND ALGORITHMS IN C++, GOODRICH, TAMASSIA.
Lists1 © 2010 Goodrich, Tamassia. Position ADT  The Position ADT models the notion of place within a data structure where a single object is stored 
Stack. ADS2 Lecture 1010 The Stack ADT (GoTa §5.1) The Stack ADT stores arbitrary objects Insertions and deletions follow the last-in.
CS 221 Analysis of Algorithms Data Structures. Portions of the following slides are from  Goodrich and Tamassia, Algorithm Design: Foundations, Analysis.
Stacks Presentation for use with the textbook Data Structures and Algorithms in Java, 6 th edition, by M. T. Goodrich, R. Tamassia, and M. H. Goldwasser,
© 2004 Goodrich, Tamassia Queues. © 2004 Goodrich, Tamassia Stacks2 The Queue ADT The Queue ADT stores arbitrary objects Insertions and deletions follow.
Queues1 © 2014 Goodrich, Tamassia, Goldwasser Presentation for use with the textbook Data Structures and Algorithms in Java, 6 th edition, by M. T. Goodrich,
Queues 5/11/2018 Presentation for use with the textbook Data Structures and Algorithms in Java, 6th edition, by M. T. Goodrich, R. Tamassia, and M. H.
CSCI 3333 Data Structures Stacks.
Stacks.
Queues Queues Queues.
Queues 11/9/2018 6:28 PM Queues 11/9/2018 6:28 PM Queues.
Queues 11/9/2018 6:32 PM Queues.
Queues 11/16/2018 4:18 AM Queues 11/16/2018 4:18 AM Queues.
Queues 11/16/2018 4:19 AM Queues 11/16/2018 4:19 AM Queues.
Circular queue.
Queue.
Queues 11/22/2018 6:47 AM 5.2 Queues Queues Dr Zeinab Eid.
Vectors 11/23/2018 1:03 PM Growing Arrays Vectors.
Stacks.
Queues 3/9/15 Presentation for use with the textbook Data Structures and Algorithms in Java, 6th edition, by M. T. Goodrich, R. Tamassia, and M. H. Goldwasser,
Queues 12/30/2018 9:24 PM Queues 12/30/2018 9:24 PM Queues.
Recall What is a Data Structure Very Fundamental Data Structures
CS210- Lecture 5 Jun 9, 2005 Agenda Queues
Copyright © Aiman Hanna All rights reserved
CS210- Lecture 6 Jun 13, 2005 Announcements
Vectors and Array Lists
Stacks and Linked Lists
Presentation transcript:

Stacks and Linked Lists

Abstract Data Types (ADTs) An ADT is an abstraction of a data structure that specifies – Data stored – Operations on the data – Error conditions associated with operations

Abstract Data Types (ADTs) An ADT is an abstraction of a data structure that specifies – Data stored – Operations on the data – Error conditions associated with operations Example: Registering for classes – The data stored are the courses in your schedule – The operations supported are Register(course) Unregister(course) ForceRequest(course) – Error conditions: Registering for multiple classes meeting at the same time

Stacks

Stacks store arbitrary objects (Pez in this case)

Stacks Stacks store arbitrary objects (Pez in this case) Operations – push(e): inserts an element to the top of the stack

Stacks Stacks store arbitrary objects (Pez in this case) Operations – push(e): inserts an element to the top of the stack

Stacks Stacks store arbitrary objects (Pez in this case) Operations – push(e): inserts an element to the top of the stack – pop(): removes and returns the top element of the stack

Stacks Stacks store arbitrary objects (Pez in this case) Operations – push(e): inserts an element to the top of the stack – pop(): removes and returns the top element of the stack

Stacks Stacks store arbitrary objects (Pez in this case) Operations – push(e): inserts an element to the top of the stack – pop(): removes and returns the top element of the stack

Stacks Stacks store arbitrary objects (Pez in this case) Operations – push(e): inserts an element to the top of the stack – pop(): removes and returns the top element of the stack – top(): returns a reference to the top element of the stack, but doesn’t remove it

Stacks Stacks store arbitrary objects (Pez in this case) Operations – push(e): inserts an element to the top of the stack – pop(): removes and returns the top element of the stack – top(): returns a reference to the top element of the stack, but doesn’t remove it Optional operations – size(): returns the number of elements in the stack – empty(): returns a bool indicating if the stack contains any objects

Stack Exceptions Attempting to execute an operation of ADT may cause an error condition called an exception Exceptions are said to be “thrown” by an operation that cannot be executed In the Stack ADT, pop and top cannot be performed if the stack is empty Attempting to execute pop or top on an empty stack throws an EmptyStackException

Exercise: Stacks Describe the output and final structure of the stack after the following operations: – Push(8) – Push(3) – Pop() – Push(2) – Push(5) – Pop() – Push(9) – Push(1)

Applications of Stacks Direct applications – Page-visited history in a Web browser – Undo sequence in a text editor – Saving local variables when one function calls another, and this one calls another, and so on. Indirect applications – Auxiliary data structure for algorithms – Component of other data structures

C++ Run-time Stack The C++ run-time system keeps track of the chain of active functions with a stack When a function is called, the run-time system pushes on the stack a frame containing – Local variables and return value – Program counter, keeping track of the statement being executed When a function returns, its frame is popped from the stack and control is passed to the method on top of the stack main() { int i; i = 5; foo(i); } foo(int j) { int k; k = j+1; bar(k); } bar(int m) { … } bar PC = 1 m = 6 foo PC = 3 j = 5 k = 6 main PC = 2 i = 5

Array-based Stack A simple way of implementing the Stack ADT uses an array We add elements from left to right A variable keeps track of the index of the top element S 012 t … Algorithm size() return t + 1 Algorithm empty() return size () == 0 Algorithm pop() if empty() then throw EmptyStackException else t  t  1 return S[t + 1]

Array-based Stack (cont.) The array storing the stack elements may become full A push operation will then throw a FullStackException – Limitation of the array-based implementation – Not intrinsic to the Stack ADT S 012 t … Algorithm push(e) if t = S.length  1 then throw FullStackException else t  t + 1 S[t]  e

Performance and Limitations (array-based implementation of stack ADT) Performance – Let n be the number of elements in the stack – The space used is O(n) – Each operation runs in time O(1) Limitations – The maximum size of the stack must be defined a priori, and cannot be changed – Trying to push a new element into a full stack causes an implementation-specific exception

Growable Array-based Stack In a push operation, when the array is full, instead of throwing an exception, we can replace the array with a larger one How large should the new array be? – incremental strategy: increase the size by a constant c – doubling strategy: double the size Algorithm push(o) if t = S.length  1 then A  new array of size … for i  0 to t do A[i]  S[i] S  A t  t + 1 S[t]  o

Comparison We compare the incremental strategy and the doubling strategy by analyzing the total time T(n) needed to perform a series of n push operations Assume that we start with an empty stack represented by an array of size 1 We call amortized time of a push operation the average time taken by a push over the series of operations, i.e., T(n)/n

Incremental Strategy Analysis We replace the array k = n / c times The total time T(n) of a series of n push operations is proportional to n + c + 2c + 3c + 4c + … + kc = n + c( … + k) = n + ck(k + 1)/2 Since c is a constant, T(n) is O(n + k 2 ) = O(n 2 ) The amortized time of a push operation is O(n)

Doubling Strategy Analysis We replace the array k = log 2 n times The total time T(n) of a series of n push operations is proportional to n …+ 2 k = n  2 k + 1  1 = 3n  1 T(n) is O(n) The amortized time of a push operation is O(1)

Stack Interface in C++ Requires the definition of class EmptyStackException Most similar STL construct is vector template class Stack { public: int size(); bool isEmpty(); Type& top() throw(EmptyStackException); void push(Type e); Type pop() throw(EmptyStackException); };

template class ArrayStack { private: int capacity;// stack capacity Type *S;// stack array int t;// top of stack public: ArrayStack(int c) : capacity(c) { S = new Type [ capacity ]; t = -1; } bool isEmpty() { return t < 0; } Type pop() throw(EmptyStackException) { if ( isEmpty ( ) ) throw EmptyStackException(“Popping from empty stack”); return S [ t-- ]; } //… (other functions omitted) Array-based Stack in C++

Singly Linked List A singly linked list is a structure consisting of a sequence of nodes A singly linked list stores a pointer to the first node (head) and last (tail) Each node stores – element – link to the next node next elem node LeonardSheldonHowardRaj  head tail

Singly Linked List Node in C++ next elem node template class SLinkedListNode { public: Type elem; SLinkedListNode *next; }; LeonardSheldonHowardRaj 

Singly Linked List A singly linked list is a structure consisting of a sequence of nodes Operations – insertFront(e): inserts an element on the front of the list – removeFront(): returns and removes the element at the front of the list – insertBack(e): inserts an element on the back of the list – removeBack(): returns and removes the element at the end of the list

Inserting at the Front 1.Allocate a new node 2.Have new node point to old head 3.Update head to point to new node  LeonardSheldonHowardRaj headtail

Inserting at the Front 1.Allocate a new node 2.Have new node point to old head 3.Update head to point to new node  LeonardSheldonHowardRaj head  Penny tail

Inserting at the Front 1.Allocate a new node 2.Have new node point to old head 3.Update head to point to new node  LeonardSheldonHowardRaj head Penny tail

Inserting at the Front 1.Allocate a new node 2.Have new node point to old head 3.Update head to point to new node  LeonardSheldonHowardRaj head Penny tail

Inserting at the Front 1.Allocate a new node 2.Have new node point to old head 3.Update head to point to new node  headtail 

Inserting at the Front 1.Allocate a new node 2.Have new node point to old head 3.Update head to point to new node  Raj headtail  

Inserting at the Front 1.Allocate a new node 2.Have new node point to old head 3.Update head to point to new node 4.If tail is NULL, update tail to point to the head node Raj headtail 

Removing at the Front 1.Update head to point to next node in the list 2.Return elem of previous head and delete the node  LeonardSheldonHowardRaj headtail

Removing at the Front 1.Update head to point to next node in the list 2.Return elem of previous head and delete the node  LeonardSheldonHowardRaj headtail

Removing at the Front 1.Update head to point to next node in the list 2.Return elem of previous head and delete the node  LeonardSheldonHowardRaj headtail

Removing at the Front 1.Update head to point to next node in the list 2.Return elem of previous head and delete the node  LeonardSheldonHowardRaj headtail

Removing at the Front 1.Update head to point to next node in the list 2.Return elem of previous head and delete the node  SheldonHowardRaj headtail

Removing at the Front 1.Update head to point to next node in the list 2.Return elem of previous head and delete the node  Sheldon headtail

Removing at the Front 1.Update head to point to next node in the list 2.Return elem of previous head and delete the node  Sheldon headtail 

Removing at the Front 1.Update head to point to next node in the list 2.Return elem of previous head and delete the node  Sheldon headtail 

Removing at the Front 1.Update head to point to next node in the list 2.Return elem of previous head and delete the node  Sheldon headtail 

Removing at the Front 1.Update head to point to next node in the list 2.Return elem of previous head and delete the node 3.If head is NULL, update tail to NULL  headtail 

Inserting at the Back 1.Allocate a new node 2.If tail is NULL, update head and tail to point to the new node; otherwise 1.Have the old tail point to the new node 2.Update tail to point to new node  LeonardSheldonHoward headtail

Inserting at the Back 1.Allocate a new node 2.If tail is NULL, update head and tail to point to the new node; otherwise 1.Have the old tail point to the new node 2.Update tail to point to new node  LeonardSheldonHoward headtail  Raj

Inserting at the Back 1.Allocate a new node 2.If tail is NULL, update head and tail to point to the new node; otherwise 1.Have the old tail point to the new node 2.Update tail to point to new node LeonardSheldonHoward headtail  Raj

Inserting at the Back 1.Allocate a new node 2.If tail is NULL, update head and tail to point to the new node; otherwise 1.Have the old tail point to the new node 2.Update tail to point to new node LeonardSheldonHoward headtail  Raj

Removing at the Back No efficient way of doing so ( O(n)) Typically would not use a singly linked-list if this operation is commonly used  LeonardSheldonHowardRaj headtail

Stack with a Singly Linked List We can implement a stack with a singly linked list The top element of the stack is the first node of the list The space used is O(n) and each operation of the Stack ADT takes O(1) time  t nodes elements top

Stack Summary Stack Operation Complexity for Different Implementations Array Fixed-Size Array Expandable (doubling strategy) Singly Linked List Pop() O(1) Push(o)O(1)O(n) Worst Case O(1) Best Case O(1) Average Case O(1) Top()O(1) Size(), isEmpty()O(1)

Queues

Queues store arbitrary objects Insertions are at the end of the queue and removals are at the front of the queue Main queue operations: – enqueue(e): inserts an element at the end of the queue – dequeue(): removes and returns the element at the front of the queue Auxiliary queue operations: – front(): returns the element at the front without removing it – size(): returns the number of elements stored – isEmpty(): returns a boolean value indicating if there are no elements in the queue Exceptions – Attempting to execute dequeue or front on an empty queue throws an EmptyQueueException

Exercise: Queues Describe the output and final structure of the queue after the following operations: – enqueue(8) – enqueue(3) – dequeue() – enqueue(2) – enqueue(5) – dequeue() – enqueue(9) – enqueue(1)

Applications of Queues Direct applications – Waiting lines – Access to shared resources (e.g., printer) – User input in a game Indirect applications – Auxiliary data structure for algorithms – Component of other data structures

Array-based Queue Use an array of size N in a circular fashion Two variables keep track of the front and rear – f index of the front element – r index immediately past the rear element Array location r is kept empty Q 012rf normal configuration Q 012fr wrapped-around configuration

Queue Operations We use the modulo operator (remainder of division) Algorithm size() return (N - f + r) mod N Algorithm isEmpty() return (f = r) Q 012rf Q 012fr

Queue Operations (cont.) Algorithm enqueue(o) if size() = N  1 then throw FullQueueException else Q[r]  o r  (r + 1) mod N Operation enqueue throws an exception if the array is full This exception is implementation-dependent Q 012rf Q 012fr

Queue Operations (cont.) Operation dequeue throws an exception if the queue is empty This exception is specified in the queue ADT Algorithm dequeue() if isEmpty() then throw EmptyQueueException else o  Q[f] f  (f + 1) mod N return o Q 012rf Q 012fr

Performance and Limitations - array-based implementation of queue ADT Performance – Let n be the number of elements in the queue – The space used is O(n) – Each operation runs in time O(1) Limitations – The maximum size of the queue must be defined a priori, and cannot be changed – Trying to enqueue a new element into a full queue causes an implementation-specific exception

Growable Array-based Queue In an enqueue operation, when the array is full, instead of throwing an exception, we can replace the array with a larger one Similar to what we did for an array-based stack The enqueue operation has amortized running time – O(n) with the incremental strategy – O(1) with the doubling strategy

Exercise Describe how to implement a queue using a singly-linked list – Queue operations: enqueue(x), dequeue(), size(), isEmpty() – For each operation, give the running time

Queue with a Singly Linked List We can implement a queue with a singly linked list – The front element is stored at the head of the list – The rear element is stored at the tail of the list The space used is O(n) and each operation of the Queue ADT takes O(1) time NOTE: we do not have the limitation of the array based implementation on the size of the stack b/c the size of the linked list is not fixed, I.e., the queue is NEVER full.  LeonardSheldonHowardRaj headtail

Informal C++ Queue Interface Informal C++ interface for our Queue ADT Requires the definition of class EmptyQueueException No corresponding built-in STL class template class Queue { public: int size(); bool isEmpty(); Type& front() throw(EmptyQueueException); void enqueue(Type e); Type dequeue() throw(EmptyQueueException); };

Queue Summary Queue Operation Complexity for Different Implementations Array Fixed-Size Array Expandable (doubling strategy) List Singly- Linked dequeue() O(1) enqueue(o)O(1)O(n) Worst Case O(1) Best Case O(1) Average Case O(1) front()O(1) Size(), isEmpty()O(1)

Double-Ended Queues The Double-Ended Queue, or Deque, ADT stores arbitrary objects. (Pronounced ‘deck’) Richer than stack or queue ADTs. Supports insertions and deletions at both the front and the end. Main deque operations: – insertFirst(object o): inserts element o at the beginning of the deque – insertLast(object o): inserts element o at the end of the deque – removeFirst(): removes and returns the element at the front of the deque – removeLast(): removes and returns the element at the end of the deque Auxiliary deque operations: – first(): returns the element at the front without removing it – last(): returns the element at the front without removing it – size(): returns the number of elements stored – isEmpty(): returns a Boolean value indicating whether no elements are stored Exceptions – Attempting to execute removeFirst,removeLast, front, or last on an empty deque throws an EmptyDequeException

Doubly Linked List A doubly linked list is a structure consisting of a sequence of nodes A doubly linked list stores a pointer to a special head/tail node Each node stores – element – link to the prev, next node next elem node head tail prev LeonardSheldon HowardRaj

Doubly Linked List A doubly linked list is a structure consisting of a sequence of nodes A doubly linked list stores a pointer to a special head/tail node Each node stores – element – link to the prev, next node next elem node prev head tail

Doubly Linked List Node in C++ template class DLinkedListNode { public: Type elem; DLinkedListNode *prev, *next; }; next elem node prev head tail LeonardSheldon HowardRaj

Doubly Linked List A doubly linked list is a structure consisting of a sequence of nodes Operations – insertFront(e): inserts an element on the front of the list – removeFront(): returns and removes the element at the front of the list – insertBack(e): inserts an element on the back of the list – removeBack(): returns and removes the element at the end of the list Private operations – add(n, e): inserts the element after the node n – remove(n): returns and removes the element stored in the node n

Adding a Node 1.Allocate a new node 2.Have new node point to the previous and next nodes 3.Update the previous and next nodes to point to the new node head tail LeonardSheldon HowardRaj

Adding a Node 1.Allocate a new node 2.Have new node point to the previous and next nodes 3.Update the previous and next nodes to point to the new node head tail LeonardSheldon HowardRaj Bernadette

Adding a Node 1.Allocate a new node 2.Have new node point to the previous and next nodes 3.Update the previous and next nodes to point to the new node head tail LeonardSheldon HowardRaj Bernadette

Adding a Node 1.Allocate a new node 2.Have new node point to the previous and next nodes 3.Update the previous and next nodes to point to the new node head tail LeonardSheldon HowardRaj Bernadette

Adding a Node 1.Allocate a new node 2.Have new node point to the previous and next nodes 3.Update the previous and next nodes to point to the new node head tail LeonardSheldon HowardRaj Bernadette

Adding a Node 1.Allocate a new node 2.Have new node point to the previous and next nodes 3.Update the previous and next nodes to point to the new node head tail Sheldon

Adding a Node 1.Allocate a new node 2.Have new node point to the previous and next nodes 3.Update the previous and next nodes to point to the new node head tail Sheldon

Adding a Node 1.Allocate a new node 2.Have new node point to the previous and next nodes 3.Update the previous and next nodes to point to the new node head tail Sheldon

Adding a Node 1.Allocate a new node 2.Have new node point to the previous and next nodes 3.Update the previous and next nodes to point to the new node head tail Sheldon

Removing a Node 1.Have the prev node’s next point to the next of the current node 2.Have the next node’s prev point to the prev of the current node 3.Delete the current node head tail LeonardSheldon HowardRaj

Removing a Node 1.Have the prev node’s next point to the next of the current node 2.Have the next node’s prev point to the prev of the current node 3.Delete the current node head tail LeonardSheldon HowardRaj

Removing a Node 1.Have the prev node’s next point to the next of the current node 2.Have the next node’s prev point to the prev of the current node 3.Delete the current node head tail LeonardSheldon HowardRaj

Removing a Node 1.Have the prev node’s next point to the next of the current node 2.Have the next node’s prev point to the prev of the current node 3.Delete the current node head tail LeonardSheldon HowardRaj

Removing a Node 1.Have the prev node’s next point to the next of the current node 2.Have the next node’s prev point to the prev of the current node 3.Delete the current node head tail LeonardSheldon Raj

Deque with a Doubly Linked List We can implement a deque with a doubly linked list – The front element is pointed to by head – The rear element is pointed to by tail The space used is O(n) and each operation of the Deque ADT takes O(1) time head tail LeonardSheldon HowardRaj

Performance and Limitations - doubly linked list implementation of deque ADT Performance – Let n be the number of elements in the deque – The space used is O(n) – Each operation runs in time O(1) Limitations – NOTE: we do not have the limitation of the array based implementation on the size of the deque b/c the size of the linked list is not fixed, I.e., the deque is NEVER full.

Deque Summary Deque Operation Complexity for Different Implementations Array Fixed- Size Array Expandable (doubling strategy) List Singly- Linked List Doubly- Linked removeFirst(), removeLast() O(1) O(1) – removeFirst, O(n) – removeLast O(1) insertFirst(o), InsertLast(o) O(1)O(n) Worst Case O(1) Best Case O(1) Average Case O(1) first(), lastO(1) size(), isEmpty() O(1)