Coders!!    Heads Up!!!   

If you believe that you have it in you to spot code errors, debug any program, and are a code God, read on…

But beware there are others like you…

Take guard, visors down and get ready for the battle. Keep your eyes on this site for online problems, crack them fast and elegantly and if you survive the joust, we’ll call you to battlefield Pragyan ’09. Then you can make it more personal. Race the clock, race your fellow coders and fight it out to the finish.

Codeslam Results are Out!

Codeslam is a new event at Pragyan, and we would love to hear what you thought about it. Please take a moment to fill in our feedback form.

This is an online event. Participation is possible from anywhere in the world.

The competition will consist of One Online Round with Two Sections Problem Solving Section and Debugging Section. While the first will test the speed and the implementation capability of the contestants, the second will check their debugging ability and their familiarity with debugging tools. A total of three hours time will be alloted.

• Problem Solving Round : The questions in this round will require the contestants to implement a said functionality in C/C++ within the given time frame. The questions will have enough subtelities to test the programming prowess of the contestants and their familarity with the language libraries.
• Debugging Round : This round will check the debugging ability of the contestants and their familiarity with tools like gdb.

• No teams are allowed. Only individual participation. Contestants will be disqualified in case they submit similar codes.
• All the questions will be related to C/C++ only.
• The event will be of 3 hour duration.
• They will be required to solve the given task in the allocated time and the one with the maximum credits will be declared winners.
• Points will be alloted to the contestants based on the time of submission, in case of tie, Code length and Approach followed to solve the problem will be considered.
• The codes will be evaluated using Automated Checkers.
• Any participant found indulging in forbidden network activities, malicious system calls, unauthorized modification of the contest materials etc. will be disqualified.
• The problemset will consist of two sections:
  1. Problem solving section: The problems will involve implementation of the given problem description.
  2. Debugging Section: The problems will involve modifying the given code to restore its described functionality.
• Decision of the judges will be final.

C:

• The current Standard (C99 with Technical corrigenda TC1, TC2, and TC3 included) -- http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1256.pdf
• ISO C Working Group (official Web site) -- http://www.open-std.org/jtc1/sc22/wg14/
• comp.lang.c Frequently Asked Questions-- http://c-faq.com/

C++:

• Standards Committee Page: JTC1/SC22/WG21 - C++ -- http://www.open-std.org/jtc1/sc22/wg21/
• C++ FAQ Lite by Marshall Cline -- http://www.parashift.com/c%2B%2B-faq-lite/
• SGI's STL Programmer's Guide -- www.sgi.com/tech/stl/

GCC Documentation

• GCC, the GNU Compiler Collection -- http://gcc.gnu.org/