Yes, you are right. Sample I/O is for illustration. But basically one will start testing his code with the sample cases first.
On Sep 4, 12:39 pm, cyberfish <[email protected]> wrote: > I don't think the sample I/O is intended for testing your program > (although I use it myself as a sanity check), but only for > illustrating the point. > > We are responsible for coming up with our own test cases. > > On Sep 4, 1:44 pm, Rajesh V <[email protected]> wrote: > > > Yesterday, I thought it would be good having Sample Input/Output > > separately for Small and Large Datasets. Because, yesterday I was > > testing my program for small input of Problem B with all the sample > > cases. Of course, it is my mistake, not watching that the 5th test > > case does not satisfy the constraints for small data set. But it took > > a lot of time to realize that. I was using C++, which didn't gave me > > any warning! I had an array[10][10] which lead to a segmentation > > fault, but that was also not displayed in the terminal! Instead the > > program gave wrong results and I was trying to debug for a long time. > > Then only I realized my mistake and corrected it. > > > So, my question is, why shouldn't we have separate sample I/O for > > small and large datasets. Or we just leave it as a part of the > > problem; as a part of the debugging! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-codejam" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code?hl=en -~----------~----~----~----~------~----~------~--~---
