关于前端:CS-120-Style-and-Errors

CS 120 Module 1 Open-Ended Project: Style and Errors
Due on Gradescope by 11:59pm ET on Friday, February 19th
For this project, you will create two differently-styled versions of a creative C++ class on GitHub and will
document the bugs you found in the code.
Requirements
• All of your programming files should be in a private GitHub repository in the course organization.

• Your repository must be named with the convention: M1OEP-Style-Errors-netid, where netid
  is your UVM NetID username.
• The repository should have a .gitignore file and a README file (see the GitHub-with-CLion repo
  for directions).
  • Your C++ class must have at least two private fields and at least four methods.
  • Your class should be nontrivial: at least one method must not be a constructor, getter, setter, or
  destructor.
  • Your class declaration should be in a header file and the implementation in a corresponding .cpp file.
  • You must use objects of the class to create a fully functioning program in a main.cpp file. Describe
  your program in your README file.
  • Your two style versions should be stored in different branches of your repository.
  • Your README must describe which of the two styles you like better and why.
  • The README file must also detail at least three errors that you experienced while developing this
  project.
• At least one must be a compiler error and at least one must not.
• For each bug, explain what you did to fix it.
• At least one of these explanations should include the use of the debugger.
  • All of the above must be pushed to your GitHub repository.
  • On Gradescope, submit the URL of the repository. The last commit to each branch will be graded. If
  you have more than two branches, clarify which ones should be graded in the master branch
  README file.
  Design
  Your two style versions must include the following (you can choose how to split the options between the
  two versions, and each version should have consistent style within itself):
• Hanging and Egyptian-style braces
• Camel case and snake case
• Top-of-file comments and method comments
• Variables with and without prefixes
  For details on these, see the M1GP-Style-Me repository README file.
  Grading
  The project is out of 50 points.
  5 pts Project compiles and runs. GitHub repository set up as described above.
  5 pts Class satisfies requirements described above.
• pts Style 1 satisfies requirements and is consistent throughout the files.
• pts Style 2 satisfies requirements and is consistent throughout the files.
• pts The main program is fully functional.
• pts The README file contains all that is described above.