Carefully , review the code and perform analysis as needed. Consider the following rules and recommendations and hints for items that you might want...

Carefully, review the code and perform analysis as needed. Consider the following rules and recommendations and hints for items that you might want to review. Note, that some rules and recommendations listed below may not be found as issues in the code.

 STR31-C. Guarantee that storage for strings has sufficient space for character data and the null terminator.

 MSC24-C. Do not use deprecated or obsolescent functions.

 FIO34-C. Distinguish between characters read from a file and EOF or WEOF.

 MSC17-C. Finish every set of statements associated with a case label with a break statement.

 MSC33-C. Do not pass invalid data to the asctime() function.

 MSC17-C. Finish every set of statements associated with a case label with a break statement.

 DCL20-C. Explicitly specify void when a function accepts no arguments.

 MEM30-C. Do not access freed memory.

You can use any C compiler you have access to including:

1. Windows C++ Express or Visual Studio

2. Mac X-Code C

3. Linux gcc

4. VM player with gcc (e.g. SDEV 300 Virtual machine)

Be sure you have a C environment where you can compile. Also review those code tutorial links provided in the classroom. Post a note, or contact your professor if you are having significant difficulties compiling a C program.

Once you have your environment working, reviewed and analyzed the code, and determined the rules and recommendations that are violated, you should fix the code. Be sure to document each issue by aligning the rule or recommendation and explain exactly how you fixed the issue.

Hints:

a. Make sure your C coding environment is working first. Those C tutorials will help you to test your environment.

b. Be very careful with the pointers and memory limits of the arrays. Most modern compilers attempt to protect your system resources, but you could potentially produce access violations that could lock your system up. Take your time and review the memory bounds for all of your arrays before you start making code changes

c. Start on this early. This will take you longer than you think.

Deliverables

Provide your fixed C source code along with a PDF document describing how you addressed each issue. For example, you should list the C Cert rule or recommendation for each issue and show and 4