Differences

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

--- haas:spring2018:unix:projects:upf0 [2018/02/25 22:21] – [upf0steps] wedge
+++ haas:spring2018:unix:projects:upf0 [2018/02/28 20:26] (current) – [numbers suite] wedge
@@ Line 50: / Line 50: @@
   * pipemath-20170201-09.tar.gz
-You would select the "20170201-09" one, because the date it encodes (Feb 1st, 2017 at 9am) is the most recent in that group. You will find this to be a common practice with many software projects on the internet.
+From visual inspection, you would select the "20170201-09" one, because the date it encodes (Feb 1st, 2017 at 9am) is the most recent in that group. You will find this to be a common practice with many software projects on the internet.
+Note, however, that visual inspection alone is not good enough for your steps file. New versions may be released, and your steps file needs to obtain the most recent version available. To facilitate this task, the latest and greatest version of pipemath will be listed in a file called LATEST (which you should see near the top of the directory index listing). You can make use of this file to assist you in automating the process of determining and downloading the latest version of the pipemath tools.
 Once those two steps are complete, you can begin on the tasks listed in your **TASK** file.
 ====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's 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**.
@@ Line 200: / Line 202: @@
 *:upf0:upf0steps has valid list of non-interactive instructions [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 resiliently creates local project directory [4/4]
@@ Line 207: / Line 209: @@
 *:upf0:upf0steps makes clear, effective use of wildcards [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 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 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 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 only have the solution command-line [4/4]
 </code>

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools