Harvey Mudd College
Computer Science Department
ACM Problems Page http://www.cs.hmc.edu/ACM
|TEAM||Red Shirts||JoshTitus||The Judges||EthanOtto||CharlieSolo||UppityFrosh|
|April 18, 2000|
|April 11, 2000|
|April 4, 2000|
|March 28, 2000|
|March 21, 2000|
|Filling the Gaps|
|March 7, 2000|
|February 22, 2000|
|February 15, 2000|
|Bank (Not Quite OCR) (Central European Regionals '95)|
|February 8, 2000|
|Find The Base (Arab/African Regionals '98)|
|Flying Stars Problem (NE Europe '98)|
|January 18, 2000|
acmSubmit <filename>.ccwhere acmSubmit is available in /home/dodds/ACM/TestScripts. Feel free to copy it locally if you wish.
The script will test your file against a number of inputs. The test files are available for viewing (if you get stuck) at /home/dodds/ACM/TestCode. If your program passes all of the tests (because its output matches that of the anticipated output), the script will let you know; if your code does not pass, a "diff" listing of how it failed will be printed.
Make your code with the command
g++ filename.ccto create an executable file named a.out.
To check your code, download the input and output files (right-click on the links and choose"save link as...") from above to your directory and then run
a.out < Test#.inThat will print the results to the console (standard out) for inspection. To check those results against the (hopefully) correct output file, run
a.out < Test#.in | diff - Test#.outIf nothing appears on the screen, your program's output and the actual output are identical. If they are not identical, the mismatching lines are printed to stdout.