Click here to Skip to main content
15,877,675 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
using namespace std;

void PrintArray(int arr[], int size)
    for (int i = 0; i < size ; i++)
        cout << arr[i] << " ";
void selectionSort(int arr[],int n){
    for (int i = 0; i < n-1;i++){
        for (int j = i+1; i < n;j++){
                swap(arr[i], arr[j]);
int main(){
    int arr[7] = {1,8,3,6,7,6,4};
    selectionSort(arr, 7);
    PrintArray(arr, 7);
    return 0;

What I have tried:

I have written a code for selection sort, but it does not provide the required output.

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:
private 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.

I'll give you a hint: keep a close eye on your array index values ... remember that indexes run from 0 to (N - 1) inclusive for an array of N elements. So an array of 3 elements will have valid indexes 0, 1, and 2 only.

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!
Share this answer
There is a bug in the second for statement.

You can find this sort of bug a lot easier if you give your variables meaningful names. I would suggest lowerIndex for i and upperIndex for j, then it is a lot harder to mix the two up accidentally.
Share this answer

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