lostecho/ostep-projects
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

more failure explanation

Browse Source
This commit is contained in:
Remzi Arpaci-Dusseau
2021-09-05 12:40:40 -05:00
parent 128cd49c76
commit bde7324f80
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
initial-kv/README.md
View File

@@ -146,15 +146,15 @@ tolerate crashes; none of these things are required for this project.
- **Bad command:** If the command line specifies a bad command, e.g., - **Bad command:** If the command line specifies a bad command, e.g.,
something that is not a `p`, `g`, `a`, `c`, or `d`, print out the something that is not a `p`, `g`, `a`, `c`, or `d`, print out the
warning `bad command` on a line by itself and keep processing the warning `bad command` on a line by itself and keep processing the
rest of the command line. rest of the command line; importantly, do *not* exit.
- **Unexpected error:** On any unexpected error condition, such as
malloc() failing, or failure to open a file successfully, print
out a useful error message and exit. This won't be tested, but may
be useful for you during development.
## Useful Routines ## Useful Routines
To exit, call `exit(1)`. The number you pass to `exit()`, in this case 1, is
then available to the user to see if the program returned an error (i.e.,
return a non-zero) or exited cleanly (i.e., returned 0).
For reading in the input file, the following routines will make your life For reading in the input file, the following routines will make your life
easy: `fopen()`, `getline()`, and `fclose()`. easy: `fopen()`, `getline()`, and `fclose()`.