In this project, instead of dealing with numeric data, we will work with a file containing text, or character data. Your task is to write a menu-driven text analyzer program. The program must print a menu giving the user a list of tasks which can be performed: 1. print the file's contents 2. quit the program 3. count the number of lines in the file 4. count the words in the file 5. count the sentences in the file 6. do a character analysis, including count the number of characters in the file count alphabetic characters count digit characters count punctuation characters count whitespace characters You must provide a separate function to process each option. You may assume that: Each sentence ends with a period, and the period character is not used for any other purpose. Words consist of any series of letters and/or digit characters, and are terminated with a blank, the marker, or a punctuation mark. There may be more than one blank between words. Note that because of this assumption, your program will count something like "Don't." as two words. The file is not empty - there is at least one line. The file name contains no blanks. The marker is counted as a character. The marker is not. Input The file name is input as a C-string, Menu choices must be input as characters.
Input The file name is input as a C-string, Menu choices must be input as characters. Three data files will be provided in the course web space, on the Blackboard site. The files are [url removed, login to view], [url removed, login to view], and proverb.txt. Copy these three data files onto your own disk, and put them in the same folder as your program 4 files. Bad Data Checking: if the file name entered cannot be opened, keep prompting the user until a valid file name is entered. If a menu choice is invalid, keep prompting the user until a valid choice is entered. You do not have to do any bad data checking on the actual contents of the data files. All data files are provided on the web site as Windows format text files. Please note that if you run your program on UNIX or on a Macintosh, you must convert the files provided to the text file format used by those platforms or they will not work correctly. Output and Testing For every data file, test every command at least once. Vary the order of the commands for each file (i.e. do not use the same command order for all the files). For each command, print a report giving the appropriate results for that task. Note that the program graders will test your program with various data files after it is turned in. Be sure to test bad data: invalid file names and invalid menu choices. You will find a link to a correct sample output for the [url removed, login to view] data file on the course Assignments web page. Please note that your output does not have to match this output exactly, but it must provide all required output elements and meet the style guidelines provided for this course. 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request.
3) Exclusive and complete copyrights to all work purchased. (No GPL, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site).