使用循环在C中打印图案 [英] Pattern printing in C using loops
问题描述
我必须使用循环在输出中生成以下模式：
ABCDEFGFEDCBA
ABCDEF FEDCBA
ABCDE EDCBA
ABCD DCBA
ABC CBA
AB BA
AA
但是我使用我制作的算法获得以下输出：
ABCDEFGFEDCBA
ABCDEF EDCBA
ABCDE DCBA
ABCD CBA
ABC BA
AB A
A
帮我纠正算法。
我尝试过：
#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- < span class =code-digit> 1 ; n ++）
{
printf（ ）;
}
for （ int k = 7-i; k> = 1; k--）
{
printf（ ％c，（64 + K））;
}
printf（ \ n）;
}
return 0 ;
}
编译并不意味着你的代码是对的！ ：笑：
将开发过程想象成编写电子邮件：成功编译意味着您使用正确的语言编写电子邮件 - 例如英语而不是德语 - 而不是电子邮件包含您的邮件想发送。
所以现在你进入第二阶段的发展（实际上它是第四或第五阶段，但你将在之后的阶段进入）：测试和调试。
首先查看它的作用，以及它与你想要的有何不同。这很重要，因为它可以为您提供有关其原因的信息。例如，如果程序旨在让用户输入一个数字并将其翻倍并打印答案，那么如果输入/输出是这样的：
输入预期输出实际输出
1 2 1
2 4 4
3 6 9
4 8 16然后很明显问题出在将它加倍的位 - 它不会将自身加到自身上，或者将它乘以2，它会将它自身相乘并返回输入的平方。
所以，你可以查看代码和很明显，它在某处：
int Double （ int value ）
{
return value * 值;
}
一旦你知道可能出现的问题，就开始使用调试器找出原因。在方法的第一行放置一个断点，然后运行你的应用程序。当它到达断点时，调试器将停止，并将控制权移交给您。您现在可以逐行运行代码（称为单步执行）并根据需要查看（甚至更改）变量内容（哎呀，您甚至可以更改代码并在需要时再试一次）。 />
在执行代码之前，请考虑代码中的每一行应该做什么，并将其与使用Step over按钮依次执行每一行时实际执行的操作进行比较。它符合您的期望吗？如果是这样，请转到下一行。
如果没有，为什么不呢？它有什么不同？
希望这可以帮助你找到代码的哪个部分有问题，以及问题是什么。
这是一项技能，它是一个值得开发的，因为它可以帮助你在现实世界和发展中。和所有技能一样，它只能通过使用来改善！
看起来差距是一个太大的位置，在差距之后你在右侧偏离了一个。答案是停止前一步显示空格，然后提前一步显示右侧。我会留给你调整你的循环。
你的代码没有你想象的那样，或者你不明白为什么！
有一个几乎通用的解决方案：一步一步地在调试器上运行你的代码，检查变量。
调试器在这里向你展示你的代码在做什么，你的任务是与它应该做的比较。
调试器中没有魔法，它不知道你的代码应该做什么，它没有找到错误，它只是通过显示帮助你你发生了什么事。当代码没有达到预期的效果时，你就接近了一个错误。
要查看你的代码在做什么：只需设置断点并查看代码是否正常运行，调试器允许你执行第1行第1行并在执行时检查变量。
此解决方案的缺点：
- 这是一个DIY，你是跟踪问题并找到根源的那个，这导致了解决方案。
这个解决方案的优点：
- 它也是一个很好的学习工具，因为它告诉你现实，你可以看到哪种期望与现实相符。
次要效果
- 你会为自己找到虫子感到自豪。
- 你的学习技巧会提高。
你应该很快就会发现什么是错的。
调试器 - 维基百科，免费的百科全书 [ ^ ]
掌握Visual Studio 2010中的调试 - 初学者指南 [ ^ ]
使用Visual Studio 2010进行基本调试 - YouTube [ ^ ]
1.11 - 调试你的程序（踩踏和断点）|学习C ++ [ ^ ]
调试器仅显示您的代码正在执行的操作，您的任务是与应该执行的操作进行比较。
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;
}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 16Then 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!
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.
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.
这篇关于使用循环在C中打印图案的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
