Monday, August 31, 2020

Phase IV : Progress Report [ 08.31.2020 @ 7:45 A.M. PST ]

 Team. This past weekend saw a couple of four-hour "bird-brained" coding sprints. During this time, the first eight language instances of our general-purpose controller were constructed ( C, C# [.NET], C++, Clojure, Go, Groovy, JAVA[ JME, JSE, & JEE ], and Node.js ). 

The most time consuming was the Clojure instance. It required the fewest instructions; however, the author only has limited experiences with LISP-like languages and has not coded Clojure programs before this effort. The Clojure controller for Phase IV required about 1.5 PH. 

The remaining language instances ( PHP, PERL, Python, Ruby, Rust, and TypeScript ) will be coded this afternoon or during this week or weekend. So, we might provide this deliverable after is initial proposed date of availability, 08.31.2020. It should be here by the American holiday, Labor Day, Monday, September 7, 2020.



Sunday, August 16, 2020

Road Running

Team. With the beginning of the university semester comes a flurry of activity. This is compounded by accepting a teaching assignment at a new college. New computing systems, administrative procedures, and a completely new pool of students with its own unique community culture. 

This coincides with the end of a term at the on-line program where the author teaches a programming fundamentals course in Python. Grading must be done and he must prepare for the next term before 08.31.2020. 

These are his deliverable items which coincide with the delivery of the next phase of this project. So, although he is working like a bird brain while coding (hunt-peck-think), he is running at light-speed between coding sessions. It is his goal that he can set aside a focused 16.0 PH for coding up the scripts. And, average of 1.0 PH per code snippet should be sufficient for the nature of the required enhancements for the phase.

In this step we are:

  • we are reading the "directory.scsv" file 
  • we are removing the blank lines in the file
  • we are parsing the individual lines around commas
  • we are ignoring lines which start question marks
  • we are removing all of the white space around the line's tokens
  • we are echoing this content along with the markup template file
In the next phase, we will process this "directory" file based upon the mappings that it describes. This will require the use of an associative array, dictionary, hash table, hash map, or similar structure. And, we will output the HTML markup with the placeholders replaced by the name of the method which will fill in that spot.

The last phase will involve using "dynamic" invocation for providing the proper content for the markup placeholder.

Hopefully, we can elude Wile E. Coyote and his proverbial ACME contraptions of doom which will scuttle our efforts.