Don't just say "it comes to an error". Describe the error. Clearly it isn't a compile error since it "work once", but what does it look like? For example, what is your test input, expected output, and actual output?Quote:
Originally Posted by Kernelpanic
You have some code that appears to be commented out... don't do that. It is perfectly fine when testing, but when showing your code to others, show your actual code, not commented out code because it is impossible for people to be certain if you uncommented that code or not when testing, so it is reasonable to assume that you in fact compiled the code as-is and so whatever errors you're talking about has to with the code as-is. Consequently, your claim that "But it work once only, if twice and more then it comes to an error." is unsubstantiated because you only used scanf with "%49[^\n]" once in your code, i.e., the situation in which you claim to have found an unspecified error never happened, so your claim must be false.Quote:
Originally Posted by Kernelpanic