Yes, #1, #2 and #3 are done. #6 does not depends on me at first, and #5 seems easy for everyone but not for me (what means that if I'm able to, I'll do it, and if not, another of my teammates willithamar wrote:I have seen that 3 of the 6 changes have are already take place.


When? I don't know exactly. Not before September, 16 I think, but I cannot give more exact schedule. I don't know either if we're going to wait a few weeks until version 3.x has been found to be really stable. What versions? Our first thought was upgrading to gcc 3.2. BTW, we'll post to this board and also announce it in the problemset page, with new versions and new compile flags if changed.ithamar wrote:I would like that you let me know when are you going to upgrade the compliers. Besides i would like to know exactly which compilers are you installing.
ithamar wrote:About the Java Support i also would like to know which classes and packages are supported with the new compiler that were not supported with the old one.
And we know. We're using it now because:ithamar wrote:Now in Java is the time to use THE STANDART java provided by SUN freely. I think that if you take another implementation NOT STANDART like gcj the problems that are happening now is going to be repeated in the future.
- It compiles to native code, so timing is more accurate than the VM of Sun Java.
- It uses almost the same compiler options that gpc, g++ and gcc, so it was very easy to implement in our system. This should be a problem no more, as FreePascal uses a compilation scheme quite different and it has been implemented.
- Rankings now includes all submissions in all languages. We're thought in dividing them into languages, because if we put javac the timing is going to be quite different, I think.
- We don't know for sure how well we will be able to measure the memory, the runtime errors...
- And more things I don't remember right now
Best regards,