Why don't show the Compilation Error Message from the gcj?

royjp · Post by **royjp** » Sun Dec 05, 2004 1:54 am

I have JSDK 1.42 here, my codes always compiles here, but almost always I get CE when I submit.

If its to hard to update the JSDK here, why don't let us see what was the compilation error (the message from the compiler) that has the number of the line that is with problem....

Would be easier to update the JSDK or to show the compilation error menssage?

randomtaiwanese · Post by **randomtaiwanese** » Wed Dec 15, 2004 8:58 am

i would be... euphoric... if they update the compiler...
currently they are using a compiler that supports up to J2SDK 1.1...
if they update to atleast 1.2, atlease with the BigInteger class, many problems can be sloved within milliseconds!

Sedefcho · Post by **Sedefcho** » Thu Feb 17, 2005 1:12 pm

The BigInteger has nothing to do with jdk 1.2
Even if they allow support for jdk 1.2, I doubt that
they will allow the usage of the BigInteger class. This
will make no sense. I, myself, am against that as this
will make many problems related to BigNumbers not
interesting any more.

Larry · Post by **Larry** » Fri Feb 18, 2005 5:41 pm

Many onsite programming contests do support Big Int (if they allow java, of course). Solving Big Integer is a one-trick pony - once you've done it, that's all.

I think it's useless to ask someone to do it over and over again. It's just annoying, but it's copy and paste anyhow. The "trick" is to recognize that BigInteger is needed, and nothing more.

Many problems with BigInt shouldn't be about BigInt - other than the most basic ones. It should be about combinatorics and the math behind getting that number, with the side effect that these numbers grow very fast. BigInt is usually _not_ a problem at all. If you want to do exclusively BigInt problems, then you can write your own class.. and be interested once.

You should penalize people with WA's if people does not know/realize that a problem requires BigInt, and not the fact that they now either a) copy and paste from an old solution/class or b) be frustrated as a relatively newcomer that they have to write BigInt for this specifically.

And, you're not really penalizing people who are determined anyhow. If someone really don't want to write a BigInt class, BigInteger.java is open - as in, you can see the source code. So, theortically, someone determined not to do it will just copy and paste that chunk into their code. It's moot.

Solve math problems. Not the _same_ sub-problem over and over again..