OJ Board

Can it be made possible that more number of input-output are provided for the problems.
Note that these may be separate from the test cases used to judge the program.
This would possibly eliminate many wrong submissions resulting from trivial doubts (like whether to add a new line at the end ) within the user when he gets WA many a time and
I think that there might be several fellow programmers like me who wouldnt start another
problem without getting the one on hand(which they think is most probably right), accepted.

Undoubtedly,the board serves the purpose most of the time with most of the posters giving more sample i/o when asked for it, but i think it would be a lot easier if there is a special test file (of course not for multiple answer problems and not for ones where they might give hint to answer.) It could make the website more complete.

I also agree that the i/o can be generated randomly by the user himself and he might run the tests. This technique would be useful only if he knows the answer or if it is easy to see the answer.

Please let me know your opinion.

Thanks for the reading,
bye,
ranjit.

If you are always provided critical in/out, how can you grow? No pain no gain.

it need not be critical i/o always. just tens of i/o can explain to the programmer atleast whether he is on the right track. If probably he finds that he is on the right track he atleast can look at the prospect of his pgms working/not working for the critical i/p.

This is mainly in regard to problems which have just one or two i/o and most of them proving to be elementary and not showcasing the intensity of the problem . More i/o can atleast help a pgmmer to find out what sort of a
question he is dealing with and understand it better when he couldnt figure them out from the
problem statement.

Anyway this is only my opinion. Thanks for the comment.
bye,
ranjit

The problem in giving too many sample input outputs in some problems is that these can in fact give an unnecessary clue as to how to solve the problem.Clearly the purpose of the test cases is not to tell you how to proceed but just to a small verification as to the veracity of your algo and maybe to clarify on say output formats.Sometimes the problem setter needs to let his words be ambiguous so as to not give away the trick in the question.Too many testcases can give them away.Testcases are as much important as the algorithm.

I do agree that some problems have this trivial newline problems but you gotta learn.I guess majority of the problems arent like this.

If after much hard work you are still unable to find your problem you can always turn to the board .

I think that Input and Output are very good in test case on my opinion. Because we can practise more to test all problems because its very good training for catching the exceptions in Object programming.
Because very much problems are try catch finally in real software appliacation. We cannot need them here.
Everybody wants only Accepted problems and ratio 1:1. I have ratio 1:5 and i am happy bacause I know that I am not perfect programmer.