User Tools

Site Tools


haas:spring2018:unix:projects:upf0

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
haas:spring2018:unix:projects:upf0 [2018/02/28 14:42] – [Get started] wedgehaas:spring2018:unix:projects:upf0 [2018/02/28 20:26] (current) – [numbers suite] wedge
Line 57: Line 57:
  
 ====numbers suite==== ====numbers suite====
-The numbers suite is basically a collection of command-line tools whose purpose is to display a single digit number, in accordance with the tools name.+The numbers suite is basically a collection of command-line tools whose purpose is to display a single digit number, in accordance with the tool'name.
  
 For example, when you run the **zero** tool, a **0** is displayed to STDOUT. For **one**, a **1** is displayed to STDOUT. And so on up through **nine**. For example, when you run the **zero** tool, a **0** is displayed to STDOUT. For **one**, a **1** is displayed to STDOUT. And so on up through **nine**.
Line 202: Line 202:
 *:upf0:upf0steps has valid list of non-interactive instructions [4/4] *:upf0:upf0steps has valid list of non-interactive instructions [4/4]
 *:upf0:upf0steps only copies/alters files if USER matches [4/4] *:upf0:upf0steps only copies/alters files if USER matches [4/4]
-*:upf0:upf0steps builds the various task#.cli files [4/4] +*:upf0:upf0steps builds the various task#.cli files it runs [4/4] 
-*:upf0:upf0steps squelches any STDERR output [4/4]+*:upf0:upf0steps obtains the latest pipemath release from site [4/4]
 *:upf0:upf0steps only displays specified STDOUT output [4/4] *:upf0:upf0steps only displays specified STDOUT output [4/4]
 *:upf0:upf0steps resiliently creates local project directory [4/4] *:upf0:upf0steps resiliently creates local project directory [4/4]
Line 209: Line 209:
 *:upf0:upf0steps makes clear, effective use of wildcards [4/4] *:upf0:upf0steps makes clear, effective use of wildcards [4/4]
 *:upf0:upf0steps has descriptive why and how comments [4/4] *:upf0:upf0steps has descriptive why and how comments [4/4]
 +*:upf0:upf0steps indentation used to promote scope and clarity [2/2]
 *:upf0:upf0steps defines and uses custom variables [4/4] *:upf0:upf0steps defines and uses custom variables [4/4]
-*:upf0:upf0steps uses command expansions [4/4]+*:upf0:upf0steps uses command expansions to get information [4/4]
 *:upf0:upf0steps uses a loop to drive numbers in final output [4/4] *:upf0:upf0steps uses a loop to drive numbers in final output [4/4]
 *:upf0:upf0steps automates the task when run [4/4] *:upf0:upf0steps automates the task when run [4/4]
-*:upf0:all files are organized, clear, and easy to read [2/2+*:upf0:all files are organized, clear, and easy to read [4/4
-*:upf0:task#.cli files produce correct output [4/4]+*:upf0:task#.cli files output only correct, specified data [4/4]
 *:upf0:task#.cli files use specified number tools by quantity [4/4] *:upf0:task#.cli files use specified number tools by quantity [4/4]
-*:upf0:task#.cli files squelch any STDERR output [4/4] +*:upf0:task#.cli files display no STDERR output [4/4]
-*:upf0:task#.cli files only display specified STDOUT output [4/4]+
 *:upf0:task#.cli files have solution within given constraints [4/4] *:upf0:task#.cli files have solution within given constraints [4/4]
 *:upf0:task#.cli files only have the solution command-line [4/4] *:upf0:task#.cli files only have the solution command-line [4/4]
 </code> </code>
haas/spring2018/unix/projects/upf0.1519828933.txt.gz · Last modified: 2018/02/28 14:42 by wedge