Click here to Skip to main content
15,068,645 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
I am trying to implement circular queue in the following way but the problem is the elements are not getting deleted and it gives me a statement for a number is deleted which is not even my front element. Please help me rectify it, I am stuck.

What I have tried:

#define MAX 4
#include <stdio.h>
#include <conio.h>

int Queue[MAX], front, rear;

void enqueue(int elem)
{
    if((front == 0 && rear == MAX - 1) || rear == front - 1)
    {
        printf("\n Queue overflow !");
    }
    
     if(front == -1 && rear == -1)
            front = rear = 0;
            
    else if(rear == (MAX -1) && front != 0)
        rear = 0;
    else
        rear = rear + 1;
            
    Queue[rear] = elem;
  
}

int dequeue()
{
    int t;
    if(front == -1)
    {
        printf("\n Queue underflow !");
    }
    

        t = Queue[front];
    
        if(front == rear)
            front = rear = -1;
            
        else if(front = MAX -1 )
            front = 0;
            
        else
            front = front + 1;
}

int size()
{
    return ((MAX - front + rear) % MAX + 1);
}

int isEmpty()
{
    if(front == -1)
        return 1;
        
    else
        return 0;
}

int frontfn()
{
    int t;
     
    if(front == -1)
    {
        printf("\n Queue is empty. \n ");
    }
    else
    {
        t = Queue[front];
        return t;
    }
 
}

void display()
{
    int i;
    if(isEmpty() == 1)
        printf("\n Queue is empty. \n");
        
    else if(rear < front)
    {
        for(i= front; i <= MAX - 1; i++)
            printf(" %d ", Queue[i]);
            
        for(i=0; i <= rear; i++)
            printf(" %d ", Queue[i]);
            
        printf("\n ");
    }
    else
    {
        for(i=front; i <= rear; i++)
            printf(" %d ", Queue[i]);
            
        printf("\n");
    }
}


int main()
{
    int choice, elem;
    char ch, temp;
    front = rear = -1;
 
     printf("\n1. Insert ");
     printf("\n2. Delete");
     printf("\n3. Last entered element ");
     printf("\n4. No. of elements strored ");
     printf("\n5. Is Queue empty ?");
     printf("\n6. Display");
 
 do
 {
    printf("\n Enter the operation to be carried out.\n ");
    scanf("%d", &choice);

    switch(choice)
    { 
        case 1:
            printf("\n Enter the element to be inserted :\n");
            scanf("%d", &elem);
        
            enqueue(elem);
            display();
            break;
            
        case 2:
             elem = dequeue();
             printf("\n The element deleted is %d \n", elem);
             display();
             break;
             
        case 3:
             elem = frontfn();
             printf("\n Last entered element is %d \n", elem);
             break;
             
        case 4:
             elem = size();
             printf("\n No. of elements strored are %d \n", elem);
             break;
             
        case 5:
             elem = isEmpty();
             if(elem == 1)
             {
             printf("\n Queue is empty. \n");
             }
             else
             {
             printf("\n Queue is not empty. \n");
             }
             break;
             
        case 6:
             display();
             break;
             
        default :
            printf("\n Wrong choice !!");
}

printf("\n Do you want to continue ?");
scanf("%c", &temp);
scanf("%c", &ch);
}
while (ch == 'y' || ch == 'Y');
}
Posted
Updated 26-Aug-21 6:12am

Compiling does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.

So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.

Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:
Input   Expected output    Actual output
  1            2                 1
  2            4                 4
  3            6                 9
  4            8                16
Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:
C
int Double(int value)
   {
   return value * value;
   }

Once you have an idea what might be going wrong, start using the debugger to find out why. Put a breakpoint on the first line of the method, and run your app. When it reaches the breakpoint, the debugger will stop, and hand control over to you. You can now run your code line-by-line (called "single stepping") and look at (or even change) variable contents as necessary (heck, you can even change the code and try again if you need to).
Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?
Hopefully, that should help you locate which part of that code has a problem, and what the problem is.
This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!
   
One of your problems is that the dequeue function, which should return the value of the front element, actually returns nothing (Note: The compiler should complain).
   
Quote:
Can someone please help me in correcting this circular queue implementation ?

Your code do not behave the way you expect, or you don't understand why !

There is an almost universal solution: Run your code on debugger step by step, inspect variables.
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't know what your code is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
To see what your code is doing: Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.

Debugger - Wikipedia, the free encyclopedia[^]

Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[^]
Basic Debugging with Visual Studio 2010 - YouTube[^]

1.11 — Debugging your program (stepping and breakpoints) | Learn C++[^]

The debugger is here to only show you what your code is doing and your task is to compare with what it should do.
   

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)




CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900