14,692,034 members
1.00/5 (1 vote)
See more:
I have to produce the following pattern in output using loops :

```ABCDEFGFEDCBA
ABCDEF FEDCBA
ABCDE   EDCBA
ABCD     DCBA
ABC       CBA
AB         BA
A           A```

However I got the following output using the algorithm I made :

```ABCDEFGFEDCBA
ABCDEF  EDCBA
ABCDE    DCBA
ABCD      CBA
ABC        BA
AB          A
A```

Help me correct my algorithm.

What I have tried:

```#include <stdio.h>
#include <stdlib.h>

int main()
{
int i,j;

for(i=1;i<=7;i++)
{

for(j=1;j<=8-i;j++)
{
printf("%c",(64+j));
}

for(int m=1;m<=i-1;m++)
{
printf(" ");
}
for(int n=1;n<=i-1;n++)
{
printf(" ");
}

for(int k=7-i;k>=1;k--)
{
printf("%c",(64+k));
}

printf("\n");

}

return 0;
}```
Posted
Updated 19-Sep-18 12:35pm

## Solution 1

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:
```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!

## Solution 2

It appears the gap is one spot too big and you are off by one on the right side, after the gap. The answer is to stop displaying spaces one step earlier and start displaying the right side one step earlier. I will leave it to you to adjust your loops.

## Solution 3

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.

The downside of this solution:
- It is a DIY, you are the one tracking the problem and finding its roots, which lead to the solution.
The upside of this solution:
- It is also a great learning tool because it show you reality and you can see which expectation match reality.

secondary effects
- Your will be proud of finding bugs yourself.
- Your learning skills will improve.

You should find pretty quickly what is wrong.

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.

## Solution 4

I see it this way:
```#include <stdio.h>

int main()
{
const int LETTERS = 6;
int row, col;
for (row = 0; row <= LETTERS; ++row)
{
for (col = -LETTERS; col <= LETTERS; ++col)
{
int index = col > 0 ? col : - col;
char c = index >= row ? ('A' + LETTERS) - index : ' ';
putchar(c);
}
putchar('\n');
}
return 0;
}```

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

Top Experts
Last 24hrsThis month
 OriginalGriff 343 Richard Deeming 210 Richard MacCutchan 163 TheRealSteveJudge 90 CHill60 65
 OriginalGriff 5,344 Richard Deeming 2,830 Richard MacCutchan 2,454 CPallini 1,707 Patrice T 1,340

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