In this project, you will clone a Git repository from Kit, modify the program, test it, and commit and push your changes back to Kit. This project provides practice with basic C programming and using git for the edit/add/commit/push software development cycle. (Additional Reference: The Kit Help Page Working with Kit Repositories (plain text version) covers the commands introduced in this assignment.)

You should work on this project individually. You may talk to your neighbors in class, or to friends or the TAs in the Collaboration Center, but you should submit your own work. Don't forget to document any help you receive in your program.

Clone the PowersOfTwo Project:

Throughout this course, you will be submitting your programs to Kit as Git repositories. This means that you need to start each assignment by cloning an existing Kit repository for the assignment. Some starting repositories will be empty; some will come with code for you to modify or enhance.

• Find the assignment on Kit and select Start.
• Find and copy the full repository name (e.g., git@kit.cs.kzoo.edu:r190) so you can paste it later.
• In your Linux/Unix terminal or command-line window,

          cd                      (takes you to your home directory)
          ls                      (list files; you should see the directory for this course)
          cd cs230                (now go to your directory for this course)
          git clone fullRepoName  (use the full repository name you copied above)
          ls                      (list files; you'll see short repo name, e.g., r190)
          mv repo PowersOf2       (e.g., mv r190 PowersOf2) 

Explore the Project:

• Go to your new directory (e.g., cd PowersOf2). Use the ls command to see what files are there. Read the README.txt file to learn what the program does and how to compile and run it.

  You can view a file at the command line with the cat command (e.g., cat README.txt) or you can bring up VS Code for the entire directory (code .) and then view all the files in the editor. (A dot by itself (.) refers to the current directory in Linux/Unix.)

  At the command line, compile and run the code to see if it does what the README file says it does. Remember that you can use the ls command to see what files are there before and after you compile.
• Read through the comments and code for powersOfTwo.c to see what it does. (You can read through printIntAsBinary.c too, if you want, but it uses some advanced, uncommon features that are beyond the scope of this project.)

Modify the PowersOfTwo Project:

• Edit the powersOfTwo.c source file to add a loop so that the program prints the powers of 2 up to (and including) 2⁸, as it claims to do. Save the file, then compile and run the program. Continue with this cycle to debug the program, as necessary.

  ⇒ What happens with 2⁸? What change do you need to make to how you are calling printIntAsBinary to print the binary value correctly?

  As specified in the syllabus, your program should adhere to the Kalamazoo College CS Program Style Guide and Documentation Standards, including use of the Braces Line Up style pattern.

• Modify the internal and external (README) documentation to better reflect the current state of the program. (The purpose of external documentation is to provide enough information for a new user to know how (and why) to use your program.)
• Commit your changes and push the modified program to Kit.
  • git status     to see what files you have changed.

  • git add sourceFile.c     (Or git add *.c to add all C source files.)
    Add any modified source files to the Git "staging area". You need to do this again whenever you modify a file, before committing it.

    Do NOT add your executable to the staging area. The executable is specific to your machine, or at least your architecture. Only add source files to the repository.

  • git status     to confirm that you are ready to commit.
  • git commit -m "Short description of change"
    (e.g., git commit -m "Add loop to print powers of 2 through 2^8")
  • git push     to push it to Kit.

Go Further:

• Edit the program again to print the powers of 2 up to and including 2¹². Compile, run, and debug the program, as necessary.

  ⇒ Note: Do you recognize 2¹⁰?

• Modify the internal and external (README) documentation to reflect the current state of the program.
• Add the modified files to the "staging area" and commit. Provide a short, accurate message to the commit command. Then push the modifications to Kit.

You can complete the edit/add/commit/push cycle repeatedly. In fact, pushing versions of your project while it is still under construction is a way to create backups of your work as you go.

"Turn In" the Project:

• When you're done, click on the Turn In button in Kit to signal that your project is ready to grade. (You can still edit/commit/push new changes after clicking on the Turn In button if you think of something you forgot earlier, but if the project has already been graded you will need to submit a Regrade Request in Kit to indicate that the project has been updated. Whether regrade requests are granted depends on the grader's workload and the significance of the project modifications.)