Scribd
Upload
16 views

Programming_Challenges_24-24

The document outlines various types of errors that can occur when submitting programs to a judge, including Wrong Answer, Compile Error, Runtime Error, Time Limit Exceeded, Memory Limit Exceeded, Output Limit Exceeded, Restricted Function, and Submission Error. It emphasizes the importance of carefully reviewing problem specifications and suggests using the programming language one is most familiar with, as the judge accepts C, C++, Pascal, and Java. The focus of the problems is on general problem-solving skills rather than language-specific features.

Uploaded by

Sandeep Singh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
16 views

Programming_Challenges_24-24

The document outlines various types of errors that can occur when submitting programs to a judge, including Wrong Answer, Compile Error, Runtime Error, Time Limit Exceeded, Memory Limit Exceeded, Output Limit Exceeded, Restricted Function, and Submission Error. It emphasizes the importance of carefully reviewing problem specifications and suggests using the programming language one is most familiar with, as the judge accepts C, C++, Pascal, and Java. The focus of the problems is on general problem-solving skills rather than language-specific features.

Uploaded by

Sandeep Singh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

4 1.

Getting Started

• Wrong Answer (WA) — This you should concern you, because your program
returned an incorrect answer to one or more of the judge’s secret test cases. You
have some more debugging to do.
• Compile Error (CE) — The compiler could not figure out how to compile
your program. The resulting compiler messages will be returned to you. Warning
messages that do not interfere with compilation are ignored by the judge.
• Runtime Error (RE) — Your program failed during execution due to a segmen-
tation fault, floating point exception, or similar problem. Its dying message will
be sent back to you. Check for invalid pointer references or division by zero.
• Time Limit Exceeded (TL) — Your program took too much time on at least one
of the test cases, so you likely have a problem with efficiency. Just because you
ran out of time on one input does not mean you were correct on all the others,
however!
• Memory Limit Exceeded (ML) — Your program tried to use more memory than
the judge’s default settings.
• Output Limit Exceeded (OL) — Your program tried to print too much output.
This usually means it is trapped in a infinite loop.
• Restricted Function (RF) — Your source program tried to use an illegal system
function such as fork() or fopen(). Behave yourself.
• Submission Error (SE) — You did not correctly specify one or more of the
information fields, perhaps giving an incorrect user ID or problem number.
Just to reiterate: if your program is found guilty of having a wrong answer, the judge
will not show you which test case it failed on, or give you any additional hints as to
why it failed. This is why it is so essential to review the specifications carefully. Even
when you may be sure that your program is correct, the judge may keep saying no.
Perhaps you are overlooking a boundary case or assuming something which just ain’t
so. Resubmitting the program without change does you absolutely no good. Read the
problem again to make sure it says what you thought it did.
The judge occasionally returns a more exotic verdict which is essentially independent
of your solution. See the appropriate website for details.

1.2 Choosing Your Weapon


What programming language should you use in your battles with the judge? Most likely,
the language which you know best. The judge currently accepts programs written in
C, C++, Pascal, and Java, so your favorite language is probably available. One pro-
gramming language may well be better than another for a specific programming task.
However, these problems test general problem-solving skills far more than portabil-
ity, modularity, or efficiency, which are the usual dimensions by which languages are
compared.

You might also like