Karel the Robot, Part VI

This is problem 7 from §6.4 (p. 153) of the Karel the Robot text.

Unless you have made arrangements with me in advance, any Karel programs you write must be handed in as printouts from the Karel software. This means that you will need to plan in advance, since, as many of you know, the printer queues can be quite long. Please staple all pages together, making sure that your name and lab section are on the first page.

In addition, please e-mail your complete HW to your TA:

Lab	TA	E-mail address
L4,L6	Raj Guruprasannaraj	sg47@cse.buffalo.edu
L2,L3	Denis Mindolin	mindolin@buffalo.edu
L1,L5	Lopa Mukherjee	lm37@cse.buffalo.edu

Your e-mailed HW must be:

Mailed from *your* UB email account, not any other account or anyone else's.
Mailed before class begins on the due date.

Write a Karel program that converts the following initial situation into the following final situation:

Initial Situation:

Karel is somewhere between the origin and 1st Street & Nth Avenue.
He has an infinite number of beepers in his beeper bag (this just means that he'll never run out of beepers, so you don't have to bother checking to see if he has any).
There is a single beeper at 1st Street & Nth Avenue. Call this the "marker" beeper.

Final Situation:

Karel leaves N beepers at the origin.
Everything else is left unspecified. This means that it doesn't matter where Karel is at the end or which direction he's facing, and it doesn't matter whether the "marker" beeper is still at 1st Street & Nth Avenue. (However, if you write an efficient program, the marker beeper will disappear!)

That's it!

(Need a hint? Click here. But try to solve the problem before looking at the hint!)

A word on grading:

The easiest way for us to grade this is to give you an "A" if you have a working program that does what it's supposed to do, a "D" if you don't have a working program and what you do have is hopeless, and a "C" for anything in between (see my "How I Grade" website for the theory behind this "triage" system of grading; "F" is reserved for those who do nothing).

However, to alleviate this easy-on-us, apparently-hard-on-you grading scheme, you can get partial credit (to boost a "C" or "D" to something higher) by submitting a Bug Report: a document that describes how your program is not working and what you would do to fix it if only you had a few more days to work on it. A good bug report can boost a poor grade to at least a "B".

Bug reports should be prepared on a word-processor or text-editor; for general advice on writing, see my "How to Write" website.

You should probably choose this option if you do not have a working program by Tuesday, Dec. 7.

DUE: AT THE START OF LECTURE: WED., DEC. 8