$30
This project will expand Project 2 by adding additional functionality, using pointers, and implementing abstract data types (ADTs) through classes. Pointers must be used for all array manipulation, including arrays with ADTs (structs, classes) e.g, rental cars, rental agencies. Pointers must be used in function prototypes and function parameter lists - not square brackets. Make sure all your C-string functions (e.g. string copy, string compare, etc.) work with pointers (parameters list and function implementation). Square brackets are to be used only when declaring an array. For this project, pointers can only be moved by conducting post/preincrement/decrement operations on them (i.e., ++ or - -), or by setting the pointer back to the base address using the array name. All pointers must be passed by value. (Note: Try to use the arrow operator (->) with Class Object pointers for member access, if you use such in your code.) The new functionality is as follows: You are given an updated data file (e.g. Agencies.txt) where there are 3 rental Car Agency locations, where each of the 3 locations (RentalAgency) has 5 cars (RentalCar). You will have similar menu options, but the functionality has been updated below. Note: using multiple helper functions to do smaller tasks will make this project significantly easier. You may want to create a function that will get a car from a location based on the location and car indices. The RentalCar Class will contain the following data members: m_year, an int (year of production) m_make, a C-string (char array of 255 maximum size) m_model, a C-string (char array of 255 maximum size) m_price, a float (price per day) m_available, a bool (1 = true; 0 = false; try to display true/false using the "std::boolalpha" manipulator like: cout << boolalpha << boolVariable; ) and will have the following methods: Default Constructor – will set the aforementioned data members to default initial values (Hint: Remember to use properly named constants where appropriate). Parameterized Constructor – will create a new object based on the values passed into it (All the above values are expected to be present in the function parameters list, and all should be used to initialize the instantiated Object member variables). Separate Get and Set methods for all data members. Print – will print out all the car’s data. EstimateCost – will estimate the car’s cost given (via a parameter passed to it) a number of days to rent it for. The RentalAgency ADT will be a struct and will contain the following data members: name, a C-string (char array of 255 maximum size) zipcode, an int array of size 5 (Hint: You will NOT be able to use cin and cout –or any fstream objects– directly with this int array as you were doing so far with C-strings. The reason is that reading/writing is specially handled by C++ for char array types. You will need to manage reading/writing to an int array on your own.) inventory, an array of RentalCar objects with a size of 5 The menu must have the following entries, each implementing a functionality: 1) Ask the user for the input file name, and then read ALL data from that file. Then, read ALL data from that file (the file has been structured where the first line is the Car Agency info, followed by 5 cars). The data have to be stored into arrays of Class Objects. 2) Print out to terminal ALL data for all Agencies and all their corresponding Cars in a way that demonstrates this relationship (see Sample Output section). 3) Estimate car rental cost - prompt for: a) an Agency (e.g., Hertz – you can do so with a 1-3 int number per-Agency), and b) a Car number (where 1-5 are the cars at each agency). 4) Find the most expensive Car – Print to terminal the single most expensive Car out of all 3 Agencies. 5) Print out only the available Cars - from all Agencies, to a separate output file (when the user chooses menu entry 5, they should also get asked for an output file name). 6) Exit program. The following minimum functionality and structure is required: Ask the user for the input file name. The list(s) of cars must be stored into array(s) of Class Objects. Use character arrays to hold your strings (i.e., C-style) exclusively (using the string data type is still not allowed). Write multiple functions (Hint: each menu option should be a function). At least on function must use pass by-Reference. Otherwise, as before, you are free to use pass by-Value, pass by-Reference, pass by-Address for your function parameters. (Note: Remember that using pass by-Value will make the function work on a local internal copy of whatever variable you pass as an argument, therefore the change will not be made on the actual argument itself, and it will be left unaffected after the function call is complete). Pointers must be used for all array manipulation (iterating over elements to read/modify cannot be performed with bracket operator accessing). Pointers must be used in function prototypes and function parameter lists (the bracket notation is not allowed in parameters lists). Pointers can only be moved by incrementing or decrementing: double d[3] = {1,2,3}; double* d_Pt = d; for (int i=0; i<3; ++i,++d_Pt){ cout << *d_Ptd; } Or by setting the pointer back to the base address using the array name. d_Pt = d; cout << *d_Pt << endl; Write your own C-string copy, C-string compare functions. Their prototypes will have the form (you must use the prototypes exactly as provided, with char * parameters): // copies characters from source to destination until a NULLcharacter ‘\0’ is found in source, then it NULL-terminates destination too, and returns void myStringCopy(char * destination, const char * source); // returns 0 when the strings match, i.e. their characters are equal one-by-one until a NULL-character ‘\0’ is found in both strings and at the same position as well // returns a value <1 if the first character that does not match has a lower value in str1 than in str2 // returns a value >1 if the first character that does not match has a higher value in str1 than in str2 int myStringCompare(const char * str1, const char * str2); The other functionality and structure of the program should remain the same as Project #2, including writing to screen and file, as well as restrictions on string libraries, global variables and constants, etc. Implement the concepts of encapsulation and data hiding as much as possible! This is a chance to experiment as much as possible with classes, and their concepts as taught in class. It is not a strict requirement that all RentalCar data members are private at this point. Try your best in order to acquaint yourself with these new concepts at this early point, so that it pays off in future project which will impose such hard requirements. Sample Output for menu option 2: Hertz 93619 2014 Toyota Tacoma , $115.12 per day , Available: true 2012 Honda CRV , $85.1 per day , Available: false 2015 Ford Fusion , $90.89 per day , Available: false 2013 GMC Yukon , $110.43 per day , Available: false 2009 Dodge Neon , $45.25 per day , Available: true Alamo 89502 2011 Toyota Rav4 , $65.02 per day , Available: true 2012 Mazda CX5 , $86.75 per day , Available: true 2016 Subaru Outback , $71.27 per day , Available: false 2015 Ford F150 , $112.83 per day , Available: true 2010 Toyota Corolla , $50.36 per day , Available: true Budget 93035 2008 Ford Fiesta , $42.48 per day , Available: false 2009 Dodge Charger , $55.36 per day , Available: true 2012 Chevy Volt , $89.03 per day , Available: false 2007 Subaru Legacy , $59.19 per day , Available: false 2010 Nissan Maxima , $51.68 per day , Available: true The completed project should have the following properties: Written, compiled and tested using Linux. It must compile successfully using the g++ compiler on department machines. Instructions how to remotely connect to department machines are included in the Projects folder in WebCampus. The code must be commented and indented properly. Header comments are required on all files and recommended for the rest of the program. Descriptions of functions commented properly. A one page (minimum) typed sheet documenting your code. This should include the overall purpose of the program, your design, problems (if any), and any changes you would make