JamesFlare/CSCI-1200
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

updating hw1 readme

Browse Source
This commit is contained in:
Jidong Xiao
2024-01-08 13:04:19 -05:00
parent a9fbfc1f21
commit 53789a6788
1 changed files with 25 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

49
hws/01_spotify_playlists/README.md
View File

@@ -30,42 +30,43 @@ After this dragging action, now, track 1 is still "Perfect Duet", track 2 is "I'
## Command Line Arguments ## Command Line Arguments
Your program will expect 4 command line arguments. The first is the name of the input file. The second is Your program will support 3 commands.
the name of the output file. The third argument is
The fourth argument will be ### Command 1: add a music track
Here are examples of valid command lines for your program: The first argument is the name of an input file which contains a playlist. The second argument is the name of another input file which contains all available music tracks. The third argument is the output file. The fourth argument is the action, which in this case is "add". The fifth argument is the title of the music track.
```console ```console
./nyplaylists.exe playlist1.txt output.txt add ./nyplaylists.exe playlist.txt library.txt output.txt add title
./nyplaylists.exe playlist1.txt output.txt remove
./nyplaylists.exe playlist1.txt output.txt reorder old new
./nyplaylists.exe playlist1.txt output.txt skip count
``` ```
You should implement very simple error checking to ensure that 4 arguments are provided and that the ### Command 2: remove a music track
input and output file streams are successfully opened. You should also check that the values for the third The first argument is the name of an input file which contains a playlist. The second argument is the name of another input file which contains all available music tracks. The third argument is the output file. The fourth argument is the action, which in this case is "remove". The fifth argument is the title of the music track.
and fourth arguments are valid. Your program should exit gracefully with a useful error message sent to
std::cerr if there is a problem with the arguments.
You must follow the specifications for the command line, input file, and output file exactly to ensure you ```console
receive full credit from the Submitty homework submission autograder. We have provided sample input & ./nyplaylists.exe playlist.txt library.txt output.txt remove title
output files on the course website. Examples of using command line arguments can be found on the course ```
webpage: [Programming Information](https://www.cs.rpi.edu/academics/courses/fall23/csci1200/programming_information.php).
### Command 3: move a music track to a new position
The first argument is the name of an input file which contains a playlist. The second argument is the name of another input file which contains all available music tracks. The third argument is the output file. The fourth argument is the action, which in this case is "move". The fifth argument is the title of the music track. The sixth argument is the new position - where this user wants the music track to be located on the playlist. Note that, unliked array indexing in C/C++, positioning in Spotify starts at 1, as opposed to 0. This can be seen in the above Spotify screenshot: the first position is position 1.
```console
./nyplaylists.exe playlist.txt library.txt output.txt move title [new_position]
```
You should implement very simple error checking to ensure that 5 or 6 arguments are provided and that the input and output file streams are successfully opened. You should also check that the value for the fifth argument is valid. Your program should exit gracefully with a useful error message sent to std::cerr if there is a problem with the arguments.
You must follow the specifications for the command line, input file, and output file exactly to ensure you receive full credit from the Submitty homework submission autograder. We have provided sample input & output files on the course website. Examples of using command line arguments can be found on the course
webpage: [Programming Information](https://www.cs.rpi.edu/academics/courses/spring24/csci1200/programming_information.php).
## Submission Details ## Submission Details
Use good coding style when you design and implement your program. Organize your program into functions: Use good coding style when you design and implement your program. Organize your program into functions: don’t put all the code in main! Be sure to read the [Homework Policies](https://www.cs.rpi.edu/academics/courses/spring24/csci1200/homework_policies.php) as you put the finishing touches on your solution. Be sure to make up new test cases to fully debug your program and don’t forget to comment your code! Complete the provided template [README.txt](./README.txt). You must do this assignment on your own, as described in the [Collaboration Policy & Academic Integrity](https://www.cs.rpi.edu/academics/courses/spring24/csci1200/academic_integrity.php) page. If you did discuss the problem or error messages, etc. with anyone, please list their names in your README.txt file. Prepare and submit your assignment as instructed on the course webpage. Please ask a TA if you need help preparing your assignment for submission.
don’t put all the code in main! Be sure to read the [Homework Policies](https://www.cs.rpi.edu/academics/courses/fall23/csci1200/homework_policies.php) as you put the finishing touches on your solution. Be sure to make up new test cases to fully debug your program and don’t forget
to comment your code! Use the provided template [README.txt](./README.txt) file for notes you want the grader to read.
You must do this assignment on your own, as described in the [Collaboration Policy & Academic Integrity](https://www.cs.rpi.edu/academics/courses/fall23/csci1200/academic_integrity.php) page. If you did discuss the problem or error messages, etc. with anyone, please list their names in your
README.txt file. Prepare and submit your assignment as instructed on the course webpage. Please ask a TA
if you need help preparing your assignment for submission.
**Due Date**: 01/18/2024, 23:59pm. **Due Date**: 01/18/2024, 22:00pm.
## Rubric ## Rubric
12 pts 13 pts
- README.txt Completed (3 pts) - README.txt Completed (3 pts)
- One of name, collaborators, or hours not filled in. (-1) - One of name, collaborators, or hours not filled in. (-1)
- Two or more of name, collaborators, or hours not filled in. (-2) - Two or more of name, collaborators, or hours not filled in. (-2)