Write a wrapper script around a long division generator in order to create a functional letter division generator in the pctX style.

Please be sure to familiarize yourself with the pertinent content in:

• UNIX for the Beginning Mage (PDF)
• Harley Hahn's Guide to UNIX and Linux
• printf PDF
• pertinent command manual pages

Please familiarize yourself with the table of contents and or index of the various resources, and sample various content to connect yourself with deeper understanding into the concepts being called upon in the current activity.

Develop and test this program on your pi. Only when done, verify that it compiles on lab46.

To utilize the needed functionality for this project, you will need to ensure you have the following packages installed:

• mercurial (also installed and configured in ntr0)

NOTE: make sure you, for the purposes of your activities pertaining to this class, that you are using your SEMESTER repository.

Your program should:

• have valid, descriptive variable names of length no shorter than 4 symbols
• perform any needed checks to make sure needed things exist and are valid before proceeding
• have consistent, well-defined indentation (no less than 4 spaces per level of indentation)
  • all code within the same scope aligned to its indentation level
• have proximal comments explaining your rationale and what is going on, throughout your code
• perform the intended operation, outputting the correct/accurate information in indicated format
• at the end of your main() function, use a single return statement to conclude your code, return a 0 indicating successful operation

To obtain project data, you will need to satisfy the following prerequisites:

• be logged into lab46 (shell) as your user
• have your semester lab46 repo cloned (into ~/src/SEMESTER)
• have created the appropriate DESIG (like “cprog” or “unix”) subdirectory therein (~/src/SEMESTER/DESIG)
• have changed into that ~/src/SEMESTER/DESIG directory

If all those conditions are met, you can use the grabit tool to obtain the project, as follows:

lab46:~/src/SEMESTER/DESIG$ grabit DESIG ldg0
make: Entering directory '/var/public/SEMESTER/DESIG/ldg0'
'/var/public/SEMESTER/DESIG/ldg0/Makefile' -> '/home/USER/src/SEMESTER/DESIG/ldg0/Makefile'
'/var/public/SEMESTER/DESIG/ldg0/README' -> '/home/USER/src/SEMESTER/DESIG/ldg0/README'
'/var/public/SEMESTER/DESIG/ldg0/ldg0.sh' -> '/home/USER/src/SEMESTER/DESIG/ldg0/ldg0.sh'
'/var/public/SEMESTER/DESIG/ldg0/ref_ldg0.aarch64' -> '/home/USER/src/SEMESTER/DESIG/ldg0/ref_ldg0.aarch64'
'/var/public/SEMESTER/DESIG/ldg0/ref_ldg0.armv7l' -> '/home/USER/src/SEMESTER/DESIG/ldg0/ref_ldg0.armv7l'
'/var/public/SEMESTER/DESIG/ldg0/ref_ldg0.x86_64' -> '/home/USER/src/SEMESTER/DESIG/ldg0/ref_ldg0.x86_64'
make: Leaving directory '/var/public/SEMESTER/DESIG/ldg0'
lab46:~/src/SEMESTER/DESIG$ 

At which point you can change into the newly created and populated ldg0 directory.

If you don't have a monitor, you likely are logging into your pi remotely (doable, and good intra-system practice)

Once your ldg0 project files are 'hg' added to your repository on lab46, commit and push.

On your pi, to obtain those files there, be sure to be in your repository, and 'hg' pull and update.

NOTE: To avoid repository conflicts, ALWAYS check for any incoming pull/update transactions before doing a commit/push. Problems occur when you forget (this is an issue on both lab46 and your pi).

Run your script:

lab46:~/src/SEMESTER/DESIG/ldg0$ ./ldg0.sh

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/version the source code in a repository
• 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:~/src/SEMESTER/DESIG/ldg0$ make submit

Project backup process commencing

Taking snapshot of current project (ldg0)      ... OK
Compressing snapshot of ldg0 project archive   ... OK
Setting secure permissions on ldg0 archive     ... OK

Project backup process complete

Submitting DESIG project "ldg0":
    -> ../ldg0-DATESTAMP-HOUR.tar.gz(OK)

SUCCESSFULLY SUBMITTED
lab46:~/src/SEMESTER/DESIG/ldg0$ 

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:ldg0:final tally of results (78/78)
*:ldg0:obtained via grabit by Sunday before deadline [6/6]
*:ldg0:script contains no syntax errors [6/6]
*:ldg0:script contains no logical errors [6/6]
*:ldg0:script contains no runtime errors [6/6]
*:ldg0:script performs stated task/algorithm [6/6]
*:ldg0:script output conforms to formatting expectations [6/6]
*:ldg0:proper error checking and status reporting performed [6/6]
*:ldg0:code implements solution using relevant concepts [6/6]
*:ldg0:code updates committed/pushed to lab46 semester repo [6/6]
*:ldg0:code uses correct variable types and name lengths [6/6]
*:ldg0:project is submitted with relevant and complete source [6/6]
*:ldg0:project is submitted on lab46 using 'make submit' [6/6]
*:ldg0:runtime tests of submitted program succeed [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