Week of June 2, 2014 beer games.

Due: Monday, June 9 as close to 4:35 pm MST as possible.

Develop a program that takes two inputs, a text file and a key (the key can be any ascii string but the text file could be any text encoding) and outputs a text file. The program searches the text file for the key. If the key is found the program inserts the number of occurrences of the key up to that point in the document next to that key. The original challenge was to have changes in-place, but I'm the only one that followed that so now it's an out-of-place challenge.

Given the following text file

hi my name is bacon and this email is getting longer than expected. have you ever thought about bacon ^ bacon && bacon?

and our key is "bacon", then the resulting text file could be:

hi my name is bacon(1) and this email is getting longer than expected. have you ever thought about bacon(2) ^ bacon(3) && bacon(4)?

You can use any languages/libraries/hax. Whoever completes the program is invited to a bar to drink beer. Whoever "wins" the challenge chooses the bar

Contestants can enter any number of programs. Programs can use any language, libraries, or dependencies. The programs will be evaluated on ONE agreed upon machine.

Make a folder in the root directory of the repository. The name of this folder is your handle, you can choose anything except "DasBoot" (that's where we'll keep all the tests and benchmarking stuff). Put all your submissions in this folder, you may organize them as you see fit.

For those not fammiliar with Git, if I wanted to submit my program called SortingIPAs.sh I could use the following procedure:

git clone https://github.com/henrylbseaworth/beergames0214.git
cd beergames0214

#create my folder/handle and copy in my submission
mkdir -p baconsSubs && cp SortingIPAs.sh baconsSubs/

git add baconsSubs/SortingIPAs.sh #add my submission to be tracked 
git commit -m "added my submission yay!"    #commit this change to the stage
git push -u orign master    #push my changes to the repo

Another Git-tip: it's a good idea to always pull before making changes and before pushing changes. For example if you run bash git pull before editing/commiting you'll save a bit of headeach if your changes affect other people's changes. This shouldn't be an issue here but since we're all trying to learn ;D

###Metrics Challenges should include details such as the due date and specifics of how to win the challenge. Usually an auto-checker will be provided to provide logical validation and possibly some benchmark if applicable.

By tradition, the winner of the challenge picks a celebration venue (bar). All contestants that complete the challenge are invited to the celebration and are not obligated to buy the winner anything.