This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
haas:spring2020:cprog:projects:sam0 [2020/03/09 15:49] – [Background] wedge | haas:spring2020:cprog:projects:sam0 [2020/03/27 14:15] (current) – [Sample execution: encode] wedge | ||
---|---|---|---|
Line 42: | Line 42: | ||
* Naming your program **decode** will invoke the decoding functionality. | * Naming your program **decode** will invoke the decoding functionality. | ||
* Mode auto-detection should work regardless of any prefixing path information (**./ | * Mode auto-detection should work regardless of any prefixing path information (**./ | ||
- | * you may want to explore the **strtok(3)** | + | * you may want to explore the **strtok(3)** |
Your program needs to: | Your program needs to: | ||
Line 60: | Line 60: | ||
Your program should be a "one shot". It should only perform its intended operation and exit. No prompting for encode/ | Your program should be a "one shot". It should only perform its intended operation and exit. No prompting for encode/ | ||
- | When compiling, an additional constraint is added: compile with the **-Wall** | + | When compiling, an additional constraint is added: compile with the **-Wall** |
====Sample execution: encode==== | ====Sample execution: encode==== | ||
Via positive command-line key: | Via positive command-line key: | ||
Line 68: | Line 68: | ||
" | " | ||
" | " | ||
+ | emmbzwc | ||
+ | goodbye | ||
^D | ^D | ||
lab46: | lab46: | ||
</ | </ | ||
- | (**NOTE:** ^D indicated the CTRL-d sequence, which generates an EOF). | + | **NOTE:** ^D indicated the CTRL-d sequence, which generates an EOF. That is the keypress you use to terminate the program; do NOT have your program display ' |
Via negative command-line key: | Via negative command-line key: | ||
Line 144: | Line 146: | ||
* Code must compile cleanly (no warnings or errors) | * Code must compile cleanly (no warnings or errors) | ||
- | * Use the **-Wall** | + | * Use the **-Wall** |
* Output must be correct, and resemble the form given in the sample output above. | * Output must be correct, and resemble the form given in the sample output above. | ||
* Code must be nicely and consistently indented (you may use the **indent** tool) | * Code must be nicely and consistently indented (you may use the **indent** tool) | ||
Line 165: | Line 167: | ||
You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches. | You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches. | ||
+ | |||
+ | =====Evaluation Criteria===== | ||
+ | |||
+ | What I will be looking for: | ||
+ | |||
+ | < | ||
+ | 78: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *:sam0:sam0 runtime output conforms to specifications [26/26] | ||
+ | </ | ||
+ | |||
+ | Additionally: | ||
+ | * Solutions not abiding by spirit of project will be subject to a 25% overall deduction | ||
+ | * Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction | ||
+ | * Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction | ||
+ | * Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction |