Skip to main content

Stack implementation using linked list

A stack data structure is a versatile data structure which is useful whenever we want output to be reverse of input, or we want a LIFO - last in first out behavior
Image from Wikipedia
.

A function call in most languages employs a stack. The parameters and local variables are pushed to call stack. And a return statement pops out most recent call stack.

Similarly when we want to check if an expression has balanced brackets, we can use a stack to store brackets.

Top of stack:

 Unlike a linked list where elements can be added to the end of list or beginning of a list, values are always added to the top of the stack. Just like a plate is added to the top of a stack of plates.

And a value is always removed from top of the stack - similar to a stack of plates again.

A stack abstract data type should define three functions
  1. push - push function inserts a value at the top of stack 
  2. pop - pop function removes a value from top of stack
  3. isempty - isempty function checks if the stack is empty
  4. peek or top - this gives the value at the top of stack
Implementation

A stack can be implemented using an array or a linked list. In both these implementations, all of the 4 functions will have O(1) time complexity. In array implementation top will be the index in array.

Let us look at linked list implementation of a stack

Linked List implementation:

In linked list implementation of stack, top of stack can be a node pointer just like head. And to push a value to stack, a node should be added to beginning of list.


NODEPTR push(NODEPTR top,NODEPTR newnode)
{
newnode->next = top;
top = newnode;
return top;
}



To pop a value from stack, a node must be deleted from beginning of linked list.


int pop(NODEPTR *topPtr)
{
if(isempty(*topPtr))
return ERROR;
int num = (*topPtr)->n;
NODEPTR temp = *topPtr;
*topPtr = (*topPtr)->next;
free(temp);
return num;
}

And checking whether the stack is empty is just checking if top is NULL.

int isempty(NODEPTR top)
{
return top==NULL;
}

 Here is the driver  program.


#include<stdio.h>  
#include<stdlib.h>
#define ERROR -1000
struct node
{
int n;
struct node *next;
};
typedef struct node * NODEPTR;

NODEPTR create_node(int value)
{
NODEPTR temp = (NODEPTR) malloc(sizeof(struct node));
temp->next = NULL;
temp->n = value;
return temp;
}
NODEPTR push(NODEPTR top,NODEPTR newnode)
{
newnode->next = top;
top = newnode;
return top;
}
int isempty(NODEPTR top)
{
return top==NULL;
}
int pop(NODEPTR *topPtr)
{
if(isempty(*topPtr))
return ERROR;
int num = (*topPtr)->n;
NODEPTR temp = *topPtr;
*topPtr = (*topPtr)->next;
free(temp);
return num;
}

int main()
{
NODEPTR top = NULL;
NODEPTR nd;

while(1)
{
int option,value;
printf("Enter 1- push 2- pop 3 - exit");
scanf("%d",&option);
if(option==3)
break;
switch(option)
{
case 1: printf("new value to push=");
scanf("%d",&value);
nd = create_node(value);
top = push(top,nd);
break;
case 2: value = pop(&top);
if(value==ERROR)
printf("Stack empty\n");
else
printf("Value popped is %d\n",value);
break;
}
}
}


Comments

Popular posts from this blog

Introduction to AVL tree

AVL tree is a balanced binary search tree where the difference between heights of two sub trees is maximum 1. Why balanced tree A binary tree is good data structure because search operation here is of the order of O(logn). But this is true if the tree is balanced - which means the left and right subtrees are almost equal in height. If not balanced, search operation will take longer.  In worst case, if the tree has only one branch, then search is of the order O(n). Look at this example.  Here all nodes have only right children.  To search a value in this tree, we need upto 7 iterations, which is O(n). So this tree is very very inefficient. One way of making the tree efficient is to, balance the tree and make sure that height of two branches of each node are almost equal. Height of a node Height of a node is the distance between the node and its extreme child.  In the above a diagram, height of 37 is 3 and height of left child of 37 is 0 and right child of 37 is 2. Bal...

Reverse a singly linked list

One of the commonly used interview question is - how do you reverse a linked list? If you talk about a recursive function to print the list in reverse order, you are so wrong. The question is to reverse the nodes of list. Not print the nodes in reverse order. So how do you go about reversing the nodes. You need to take each node and link it to previous node. But a singly linked list does not have previous pointer. So if n1 is current node, n2 = n1->next, you should set     n2->next = NULL But doing this would cut off the list at n2. So the solution is recursion. That is to reverse n nodes  n1,n2,n3... of a list, reverse the sub list from n2,n3,n4.... link n2->next to n1 set n1->next to NULL The last step is necessary because, once we reverse the list, first node must become last node and should be pointing to NULL. But now the difficulty is regarding the head? Where is head and how do we set it? Once we reach end of list  viz n1->next ==NULL, th...

Balanced brackets

Have you observed something? When ever you are writing code using any IDE, if you write mismatched brackets, immediately an error is shown by IDE. So how does IDE  know if an expression is having balanced brackets? For that, the expression must have equal number of opening and closing brackets of matching types and also they must be in correct order. Let us look at some examples (a+b)*c+d*{e+(f*g)}   - balanced (p+q*[r+u )] - unbalanced (p+q+r+s) ) - unbalanced (m+n*[p+q]+{g+h}) - balanced So we do we write a program to check if an expression is having balanced brackets? We do need to make use of stack to store the brackets. The algorithm is as follows Scan a character - ch from the expression If the character is opening bracket, push it to stack If the character is closing bracket pop a character from stack If popped opening bracket and ch are not of same type ( ( and ) or [ and ] ) stop the function and return false Repeat steps 2 and 3 till all characters are scanned. On...