OJ Board

scanf may return 0 or -1 on failure. So this line is wrong:

while(scanf("%ld",&n)){

You must check that scanf returns 1 here.

Yes, you may read all the input before printing the output, if you'd like.
But it's more usual to just read and solve the test cases one-by-one.

Your class should be called Main.

Yes.

On a 32-bit OS (which UVa judge uses), "unsigned long int" is an unsigned 32-bit integer, and so it can't represent 2^32, which is a possible input in this problem.

No, it ain't.

I haven't used the judge for a while, but previously they only reported which Unix signal killed your program. E.g. SIGSEGV, SIGFPE (floating point exception), SIGABRT (call to abort()), etc. But JVM doesn't crash in this way, so RE means just that JVM exited with a non-zero exit code. No other deta...

Sorry for delay.
I've put most of my ACM ICPC-related stuff here - http://github.com/infnty/acm/
My old team notebook is at http://github.com/infnty/acm/raw/master ... tebook.pdf

Do not use files. You are supposed to read from standard input (java's System.in) and write to standard output.

No, that shouldn't be a problem. A straightforward code without memoization is intended to pass.

I think the error is here - "while (scanf("%d %d", &i, &j))". It must be "while (scanf("%d %d", &i, &j) == 2)".

kiddo wrote:will the grading system recognize gmp lib?

No, UVa judge doesn't allow third-party libraries.

So, the only option I have to code it myself

Yes.

It's not very hard at all, except for the division.

by using string operation?

Using arrays, yes.

kiddo wrote:Is there a data type like Java Big Integer in C++?

No. Write one, or use a third-party library such as gmp.

Floating point types have a finite precision, and so they typically represent values with some round-off error. You should add/subtract some small value (epsilon) during comparison of floats in order to tolerate this error. E.g. instead of "a < b", it's better to write "a < b - EPS&qu...

Not all control paths in your np() function return a value. Unlike some other languages (like Lisp, where functions return value of last statement), in C/C++ you must explicitly use a "return <expression>;" statement to return some value from a function. If control exits a function but not...

Your program is supposed to read from standard input and write output to standard output (see http://en.wikipedia.org/wiki/Standard_streams). No files needed.

You are welcome to translate it if you want. Larry most likely won't mind. Translation's page name should probably be http://www.algorithmist.com/index.php/ru/UVa_515