| 6/10/06 |
Here's a solution to Homework 2.
|
| 6/7/06 |
I've reopened submission for prior problems (having already squirreled
away the solutions you've turned in so far). If there's a problem you hadn't
solved previously that has been nagging at you for a while, here's a chance to
salvage some credit on it.
|
| 5/26/06 |
Homework 2 is designed to give you practice with
exceptions. The next problem, due 9 PM, Monday, June 5, is
War [
PDF].
|
| 5/19/06 |
The Programming Challenges website problem has been fixed.
|
| 5/18/06 |
It appears the Programming Challenges website is reporting "Compilation
Error" for every submission. I've notified their administrator. Until it's
fixed, use the other judge.
|
| 5/14/06 |
Three more problems, due Tuesday, May 23, 9 PM:
Distinct Subsets [
PDF],
Bee Maja [
PDF], and
Rope Crisis in Ropeland [
PDF].
|
| 5/9/06 |
Here's a solution to Homework 1.
|
| 5/3/06 |
After today's lecture, you'll know what you need to know to do
Homework 1.
|
| 5/2/06 |
One more problem for now, due Monday, May 8, 9 PM:
Little Bishops [
PDF]. (If those links don't work, try
this one.)
|
| 4/20/06 |
The next two problems to solve are
Doublets [
PDF] and
Factovisors [
PDF]. For now, have Factovisors judged by the
Programming Challenges
website, and Doublets by either that site or the
Valladolid judge. (The Programming
Challenges judge doesn't handle problems that have multiple possible correct
outputs well, so sometimes it falsely says Wrong Answer for a correct
program; if that happens, try the other judge, since it doesn't have that
bug.) I'll try to get my submission scheme going by the due time of April
27, 9 PM.
|
| 4/18/06 |
Use the Turn in a program link in the
Contents frame to the left to turn in your solutions to Minesweeper and Jolly
Jumpers. For each problem, you'll turn in a single .cpp, .c, or .java file.
Right now, all I do is collect your programs. (Eventually, I plan to have
the program judged at the time you submit it.)
|
| 4/13/06 |
Programming contest problems read from standard input and write to
standard output. If you're running the program as a console application or
from a command line, with input from the keyboard and output to the screen,
your output may appear to be interleaved with your input. That's OK, since
the judges actually run your program with standard input and output redirected
to files. If you insist on not writing any output until all input is read
(which as I just said, you don't have to do), there's an almost trivial way
to do it using something I've talked about in class.
|
| 4/10/06 |
The first two problems to solve are
Minesweeper [
PDF] and
Jolly Jumpers [
PDF]. For now, have them judged by the
Programming Challenges
website, but by the due time of April 17 19, 9 PM, I'll have my own
submission scheme set up.
|