Program Specification

In this assignment you will create your own version of the unix command wc. You will read in a file (or multiple files) and report stats including the number of lines, words, and characters in the file. Additionally, print the total number of lines for all files at the end. If there is an option provided, print only the count that is relevant.

Your code should behave as follows:

Compile¶

Compile with the command gcc -Wall -std=c11 -o wordcount wordcount.c. Your program must compile and run without errors or warnings when compiled and executed on calgary.

Input Handling¶

The program requires one or more input files.

• If there are no input files, print the usage message and exits with EXIT_FAILURE.
• Does not need to work with redirected input.
• If an error occurs when opening or reading a file, the program should write an appropriate error message to stderr saying the file is skipped. And then, the program will continue processing any remaining files on the command line.

The program should also be able to proccess three options: -l, -w, -c.

• If an option is detected, the program will output only the number of lines, words, or characters respectively.
• If an option is specified, the program will NOT print the total number of lines in all the files.
• The program shouldn’t process more than one option. If more than one option is provided, the first one should be activated.

To simplify the option handling you will assume that any options will come before the names of the input files. In other words, if you detect any input argument string that is not a valid option, you will assume that it, and any subsequent arguments, are file names.

Be able to handle input lines containing up to 500 characters (including the terminating \0 byte). The performance for other files is undefined, and will not be evaluated.

Functionality¶

For each input file, calculate the number of lines, words, and characters.

Print a message with the results and the file name, similar to the out put of wc.

Additionally, print the total number of lines for all files if no option is provided.

Exit¶

If the program terminates prematurely because of some error, it should print an appropriate error message to stderr and exit with an exit code of EXIT_FAILURE (defined in <stdlib.h> – see the description of the exit() function).

If the program terminates normally after attempting to open and process all of the files listed on the command line, it should terminate with an exit code of EXIT_SUCCESS. This is normally done by returning this value as the int result of the main function.

Example Run¶

Your program should match the following behavior exactly:

$ ./wordcount -l
Usage: ./wordcount requires an input file.
$ echo $?
1
$ ./wordcount point.c "NON FILE" shorttext
73 247 1574 point.c
NON FILE will not open. Skipping.
4 13 68 shorttext
Total Lines = 77
$ wc point.c "NON FILE" shorttext
73  247 1574 point.c
wc: 'NON FILE': No such file or directory
4   13   68 shorttext
77  260 1642 total
$ ./wordcount -l point.c
73
$ ./wordcount -c point.c shorttext
1574
68
$ ./wordcount -l -wc shorttext
-wc will not open. Skipping.
 4

The autograder includes many more test cases, but this example demonstrates what is defined by the specification above.

Technical Requirements¶

You should pay attention to the following guidelines for meeting performance expectations.

1. Use standard C library functions where possible; do not reimplement operations available in the basic libraries. For instance, strncpy in <string.h> can be used to copy \0-terminated strings; you should not be writing loops to copy such strings one character at a time.
2. You should use “safe” versions of file and string handling routines such as fgets and strncpy instead of routines like gets and strcpy. The safe functions allow specification of maximum buffer or array lengths and will not overrun adjacent memory if used properly.
3. Since this program is likely relatively short, all of the functions should be in a single file called wordcount.c. You should arrange your code so that related functions are grouped together in a logical order in the file.
4. Your program must be robust. It should not crash (segfault or otherwise) or produce meaningless or incorrect output regardless of the contents of command line parameters or input files (except, of course, you are not required to deal with files or string parameters with lines longer than the limits given above).

Code Quality Requirements¶

As with any program you write, your code should be readable and understandable to anyone who knows C. In particular, for full credit your code must observe the following requirements.

1. Divide your program into suitable functions, each of which does a single well-defined task. For example, there should almost certainly be a function that processes a single input file, which is called as many times as needed to process each of the files listed on the command line (and which, in turn, might call other functions to perform identifiable subtasks).

2. Be sure to include appropriate function prototypes/declarations near the beginning of the file so the actual function definitions can be in a logical sequence and related functions are grouped together.

3. Comment sensibly, but not excessively. You should not use comments to repeat the obvious or explain how the C language works – assume that the reader knows C at least as well as you. Your code should, however, include the following minimum comments:

• Every function must include a heading comment that explains what the function does (not how it does it), including the significance of all parameters and any effects on or use of global variables (to the extent that there are any).
• Every significant variable must include a comment that is sufficient to understand what information is stored in the variable and how it is stored. In some cases, you may describe many variables in one comment.
• Any code based on someone else’s work (such as Stack Overflow) must include a comment for citation. Again, no chatGPT for programming!
• In addition, there should be a comment at the top of the file giving basic identifying information, including your name, the date, and purpose of the file.

4. Use appropriate names for variables and functions: nouns or noun phrases suggesting the contents of variables or the results of value-returning functions; verbs or verb phrases for void functions that perform an action without returning a value. Variables of local significance like loop counters, indices, or pointers should be given simple names like i, or p, and often do not require further comments.

5. Avoid global variables. Use parameters (particularly pointers) appropriately.

6. You may use an appropriate #define MAXLINE command to set the maximum line length mentioned above.

7. No unnecessary computation. Don’t make unnecessary copies of large data structures; use pointers. (Copies of ints, pointers, and similar things are cheap; copies of arrays and large structs are expensive.) Don’t read the input by calling a library function to read each individual character. Read the input a line at a time (it costs just about the same to call an I/O function to read an entire line into a char array as it does to read a single character). Your code should be simple and clear, not complex containing lots of micro-optimizations that don’t matter.

8. You should use the cpplint.py style checker, which is provided to you in the git repo:

• Use ./cpplint.py --clint wordcount.c to review your code. If this fails, you must call python3 explicitely: python3 ./cpplint.py --clint wordcount.c.
• There is more help for using this code on the CSE 333 page.
• While this checker may flag a few things that you wish to leave as-is (notably: You may ignore warnings about ‘strtok’), most of the things it catches, including whitespace errors in the code, should be fixed. We will run this style checker on your code to check for any issues that should have been fixed. Use the Ed or office hours if you have questions about particular clint warnings.

Implementation Hints¶

1. There are a lot of things to get right here; the job may seem overwhelming if you try to do all of it at once. But if you break it into small tasks, each one of which can be done individually by itself, it should be quite manageable. For instance, figure out how to process a single file before you implement the logic to process all of the files on the command line. (Or, vice-versa, but start small and test before you move on).

2. Think before you code. You will ultimately get the job done faster, better, and with less pain if you spend some time to sketch your design (which functions are needed? what exactly do they do? what are the main data structures?) before you write detailed code. Start coding by writing function headings and heading comments and creating significant variables – and commenting those too. Then as you write detailed code and test it you will have your written design information in the comments to compare and check as you work on the code.

3. I/O is relatively expensive, while storing one more integer is relatively inexpensive. As a result, it is likely a good idea to write one function that calculates all the potential output values in one go, and use the options to determine which ones to print to stdout.

4. Every time you add something new to your code, test it. Right Now! Immediately!! BEFORE YOU DO ANYTHING ELSE!!! It is much easier to find and fix problems if you can isolate the potential bug to a small section of code you just added or changed.

5. The standard C library contains many functions that you will find useful. In particular, look at the <stdio.h>, <string.h>, <ctype.h> and <stdlib.h> libraries.

6. strlen tells you how many characters are in a string.

7. Every file stream that is open should be subsequently closed.

8. Use the compiler -Wall option. Don’t waste time searching for errors that the compiler or run-time tests could have caught for you.

9. Be sure to test for errors like trying to open or read a nonexistent file to see if your error handling is working properly.

10. git commit early and often.