在uva-online-judge上我的问题没有497-幼儿园计数游戏的解决方案有什么问题？ [英] what's wrong with my solution for problem no 497-Kindergarten Counting Game on uva-online-judge ?
问题描述
https://uva.onlinejudge.org/index .php？option = com_onlinejudge& Itemid = 8& page = show_problem& problem = 435 [ ^ ]
我的解决方案：
https://uva.onlinejudge.org/index.php?option=com_onlinejudge&Itemid=8&page=show_problem&problem=435[^]
my solution :
#include<iostream>
#include<stdio.h>
#include<string.h>
using namespace std;
int main()
{
char str[2000];
int len,c,w=0;
while(gets(str))
{
c=0;
len=strlen(str);
int i=0;
while(i<len)>
{
if(isalpha(str[i]))
w=1;
i++;
if(str[i]==' '|| str[i]=='\0')
{
if(w==1)
c++;
w=0;
i++;
}
}
cout<<c<<"\n";
}
}
推荐答案
除了运行和查找外，您希望我们怎么知道？它的作用是什么？
当代码没有达到预期效果时，每个人都必须这样做：使用调试器。
编译并不意味着你的代码是正确的！ ：笑：
将开发过程视为编写电子邮件：成功编译意味着您使用正确的语言编写电子邮件 - 例如英语，而不是德语 - 但电子邮件包含您想要的邮件发送。
所以现在你进入第二阶段的发展（实际上它是第四或第五阶段，但你会在之后的阶段进入）：测试和调试。
首先看看它做了什么，以及它与你想要的有何不同。这很重要，因为它可以为您提供有关其原因的信息。例如，如果程序旨在让用户输入一个数字并将其翻倍并打印答案，那么如果输入/输出是这样的：
How would you expect us to know, other than by running it and finding out what it does?
So do what everyone has to when the code doesn't do what they expect: use the debugger.
Compiling does not mean your code it right! :laugh:
Think 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 - nnot 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然后很明显问题出在将它加倍的位 - 它不会将自身加到自身上，或者将它乘以2，它会将它自身相乘并返回输入的平方。
所以，你可以查看代码和很明显，它在某处：
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;
}
一旦你知道可能出现的问题，就开始使用teh调试器找出原因。在第一行代码上放置一个断点并运行您的应用程序。在执行代码之前，请考虑代码中的每一行应该做什么，并将其与使用Step over按钮依次执行每一行时实际执行的操作进行比较。它符合您的期望吗？如果是这样，请转到下一行。
如果没有，为什么不呢？它有何不同？
这是一项非常值得开发的技能，因为它可以帮助你在现实世界和发展中。和所有技能一样，它只能通过使用来改善！
是的，我可能会告诉你问题是什么 - 但这并不难做到，并且你将同时学到一些非常值得的东西！
Once you have an idea what might be going wrong, start using teh debugger to find out why. Put a breakpoint on the first line of code and run your app. 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?
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!
Yes, I could probably tell you what "the problem" is - but it's not difficult to do this yourself, and you will learn something really worthwhile at the same time!
问题描述将输入和输出标记为样本，暗示程序应该适用于任何数据。但是，您的程序将在长输入行上失败（以未定义的方式）。
成为优秀程序员的很大一部分是理解规范。另一部分是让计算机理解这些规范。
The problem description lables the in- and output as sample, implying the program should work for any data. However, your program will fail (in undefined ways) on long input lines.
A good portion of being a good programmer is understanding the specification. The other part is making the computer understand those specifications.
这篇关于在uva-online-judge上我的问题没有497-幼儿园计数游戏的解决方案有什么问题？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
