| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
sense there.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
with this repository?
Next Step:
Review the Lab0 prep work, if necessary.
|
| |
|
|
|
| |
Next Step :
Write a flowchart and/or pseudo-code for this project. Put it into a file: include this file in your GitHub project. Either include this in “run” file from Step 11 or put it in a separate file with a name that starts similarly to the other files (CST116-Lab0-<lastname>) and ends with “-flowchart” or “-pseudo-code". This file also might be something other than a text file (in order to hold the flowchart.
|
| |
|
|
|
| |
Next Step :
Copy the output from the run of your program to a text file in your project. Give the text file the same name as your project (except for the extension).
|
| |
|
|
|
| |
Next Step :
Add a cout statement that lets the world know who you are and what your GitHub is. Be sure to include your GitHub name and an endl (no /n).
|
| |
|
|
|
| |
Next Step:
Add a cout statement that lets the world know who you are and what your GitHub is. Be sure to include your GitHub name and an endl (no /n).
|
| | |
|
| | |
|
| |
|