It would be nice to be able to submit the exact same code for testing (problem A) so we can avoid compilation errors as it's very hard to test this codes locally.
For example, if there's a problem called dummy_problem where I can call NumberOfPeople() and Height(i) for 0 <= i < NumberOfPeople(), then I could include dummy_problem.h so I can call NumberOfPeople() and Height(i) so I can test that my code compiles, also for avoiding runtime errors that are very easy to avoid if the code is testable offline, you can define a compiler variable like TESTING and more functions to the interface like SetNumberOfPeople(n) and SetHeight(i,h) so I can add the following code (example in C++ but I think it's easy to do in other languages as well) #ifdef TESTING SetNumberOfPeople(10); for(int i=0;i<10;i++) SetHeight(i,180); #endif at the beginning of one of my nodes and then if I don't set a variable it returns runtime error (for example I don't call SetNumberOfPeople then if I write NumberOfPeople() it returns runtime error). This could have been very helpfull for me as I had a few runtime errors because of a small mistake I made that I was calling a function of the interface with index out of bounds and a LOT of compile errors. I know I can implement that by myself but it would have made me lose a lot of time and I think it's extremelly helpfull! Thanks, Leo.- -- You received this message because you are subscribed to the Google Groups "Google Code Jam" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-code/CA%2BE_-jScshvved%3DeSMOVfDseB1mJwVBTiUPRBqrk6qfNPPxSgQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
