问题描述
Input:
3
3 1
4 4
2 5
Output:
****
*..*
*..*
****
*..*
*..*
****
*..*
*..*
****
*************
*..*..*..*..*
*..*..*..*..*
*************
*..*..*..*..*
*..*..*..*..*
*************
*..*..*..*..*
*..*..*..*..*
*************
*..*..*..*..*
*..*..*..*..*
*************
****************
*..*..*..*..*..*
*..*..*..*..*..*
****************
*..*..*..*..*..*
*..*..*..*..*..*
****************
我的尝试：
What I have tried:
#include <iostream>
using namespace std;
int main() {
int i,j,l,c,t;
cin>>t;
while(t>0)
{
cin>>l>>c;
for(i=1;i<=3*l+1;i++)
{
if(i%3==1)
{
for(int p=1;p<=3*c+1;p++)
{
cout<<"*";
}
cout<<"\n";
}
for(j=1;j<=3*c+1;j++)
{
if(j%3==1)
cout<<"*";
else
cout<<".";
}
cout<<"\n";
}
cout<<"\n";
t--;
}
return 0;
}
我的输出结果是：
my output coming out is:
****
*..*
*..*
*..*
****
*..*
*..*
*..*
****
*..*
*..*
*..*
****
*..*
*************
*..*..*..*..*
*..*..*..*..*
*..*..*..*..*
*************
*..*..*..*..*
*..*..*..*..*
*..*..*..*..*
*************
*..*..*..*..*
*..*..*..*..*
*..*..*..*..*
*************
*..*..*..*..*
*..*..*..*..*
*..*..*..*..*
*************
*..*..*..*..*
****************
*..*..*..*..*..*
*..*..*..*..*..*
*..*..*..*..*..*
****************
*..*..*..*..*..*
*..*..*..*..*..*
*..*..*..*..*..*
****************
*..*..*..*..*..*推荐答案
cout<<"\n";
to
to
cout<<i<<"\n";
并查看每个值的打印内容我。
-----
您的代码没有按照您的预期行事，或者您没有不明白为什么！
有一个几乎通用的解决方案：一步一步地在调试器上运行你的代码，检查变量。
调试器这里是为了向您展示您的代码正在做什么，您的任务是与它应该做什么进行比较。
调试器中没有魔法，它不知道您的代码应该做什么，它没有发现错误，只是通过向您展示正在发生的事情来帮助您。当代码没有达到预期的效果时，你就接近了一个错误。
要查看你的代码在做什么：只需设置断点并查看代码是否正常运行，调试器允许你执行第1行第1行并在执行时检查变量。
此解决方案的缺点：
- 这是一个DIY，你是跟踪问题并找到根源的那个，这导致了解决方案。
这个解决方案的优点：
- 它也是一个很好的学习工具，因为它告诉你现实，你可以看到哪种期望与现实相符。
次要效果
- 你会为自己找到虫子感到自豪。
- 你的学习技巧会提高。
你应该很快就会发现什么是错的。
[]
[]
[]
[]
调试器仅显示您的代码正在执行的操作，并且您的任务是与应该执行的操作进行比较。
and see what is printed for each value of i.
-----
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.
这篇关于我必须打印图案的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！