haas:fall2021:unix:projects:mtf0
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| haas:fall2021:unix:projects:mtf0 [2020/10/17 14:20] – external edit 127.0.0.1 | haas:fall2021:unix:projects:mtf0 [2021/10/04 15:05] (current) – [bc] wedge | ||
|---|---|---|---|
| Line 115: | Line 115: | ||
| <cli> | <cli> | ||
| - | lab46: | + | lab46: |
| 4*5 | 4*5 | ||
| 20 | 20 | ||
| Line 122: | Line 122: | ||
| Because it takes input from STDIN, and sends output to STDOUT, it can be especially useful in a command pipeline. | Because it takes input from STDIN, and sends output to STDOUT, it can be especially useful in a command pipeline. | ||
| - | By default, it expects input values to be in base 10, and outputs the result in base 10. | + | < |
| + | lab46: | ||
| + | 20 | ||
| + | </ | ||
| + | By default, it expects input values to be in base 10, and outputs the result in base 10. But it possesses the ability to change the base used for output and input transactions. | ||
| + | |||
| + | NOTE: when changing the base, unless you take into account the representation of the base once the input base has been modified, change the output base before changing the input base. | ||
| ====printf==== | ====printf==== | ||
| - | The **printf** tool is an especially powerful output formatter. | + | The **printf** tool is an especially powerful output formatter. |
| + | |||
| + | =====Submission===== | ||
| + | To successfully complete this project, the following criteria must be met: | ||
| + | |||
| + | * Code must compile cleanly (no notes, warnings, nor errors) | ||
| + | * Output must be correct, and match the form given in the sample output above. | ||
| + | * Code must be nicely and consistently indented | ||
| + | * Code must be well commented | ||
| + | * Do NOT double space your code. Group like statements together. | ||
| + | * Output Formatting (including spacing) of program must conform to the provided output (see above). | ||
| + | * Track/ | ||
| + | * Submit a copy of your source code to me using the **submit** tool. | ||
| + | |||
| + | To submit this program to me using the **submit** tool, run the following command at your lab46 prompt: | ||
| + | |||
| + | < | ||
| + | lab46: | ||
| + | |||
| + | Project backup process commencing | ||
| + | |||
| + | Taking snapshot of current project (mtf0) | ||
| + | Compressing snapshot of mtf0 project archive | ||
| + | Setting secure permissions on mtf0 archive | ||
| + | |||
| + | Project backup process complete | ||
| + | |||
| + | Submitting DESIG project " | ||
| + | -> ../ | ||
| + | |||
| + | SUCCESSFULLY SUBMITTED | ||
| + | lab46: | ||
| + | </ | ||
| + | |||
| + | 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. | ||
| + | |||
| + | What I'll be looking for: | ||
| + | |||
| + | < | ||
| + | 78: | ||
| + | *: | ||
| + | *: | ||
| + | *: | ||
| + | *: | ||
| + | *: | ||
| + | *: | ||
| + | *: | ||
| + | *:mtf0:code implements solution using relevant concepts [6/6] | ||
| + | *:mtf0:code updates committed/ | ||
| + | *:mtf0:code uses readable variable names describing action [6/6] | ||
| + | *: | ||
| + | *: | ||
| + | *: | ||
| + | </ | ||
| + | |||
| + | 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 lacking **ORGANIZATION** ior are not easy to read (within 90 char width) are subject to a 25% overall deduction | ||
haas/fall2021/unix/projects/mtf0.1602944425.txt.gz · Last modified: 2020/10/17 14:20 by 127.0.0.1
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
