From 5d4eca5257a60c5f1de043fdf3f67e0a9df011f4 Mon Sep 17 00:00:00 2001 From: cassiopc Date: Wed, 8 Aug 2012 19:52:19 +0200 Subject: many small bug fixes --- boca-1.5.0/doc/problemexamples/multas/limits/java | 13 ------------- 1 file changed, 13 deletions(-) delete mode 100644 boca-1.5.0/doc/problemexamples/multas/limits/java (limited to 'boca-1.5.0/doc/problemexamples/multas/limits/java') diff --git a/boca-1.5.0/doc/problemexamples/multas/limits/java b/boca-1.5.0/doc/problemexamples/multas/limits/java deleted file mode 100644 index b48a3b7..0000000 --- a/boca-1.5.0/doc/problemexamples/multas/limits/java +++ /dev/null @@ -1,13 +0,0 @@ -#!/bin/bash -# this executable shall output the number of second of timelimit in the first line, for the given problem and with language according to this filename -echo 4 -# and the number of repetitions to run within the given timelimit in the second line -echo 10 -# and the maximum amount of memory per repetition in the third line (in Mbytes) -echo 512 -# and shall return zero to indicate no failure -exit 0 -# the idea is that this file will be executed by the autojudge in the first time the autojudge downloads a problem, so as it will be -# able to decide the proper time limit for the machine where it is running. If one wants to fix a predefined time limit, then it is -# enough to write a script like this one with the desired value. Otherwise, one can build any more sophisticated program that outputs -# the value. -- cgit v1.2.3