Write a function which will read in a phone number from the user and 'return' it to the caller. The caller is expected to prompt the user before calling your function. Recall that a phone number is actually three values: an area code, an exchange, and a line number. These three values are normally typed with/'s and/or -'s between the numbers - you need not care which symbol(s) they choose. (No, they will not place the area code in parentheses! Yes, they will type ail three numeric parts and both separation symbols. No, they will not type a '1' in front - no matter what the phone Company says!) (Thought-provoker: Why should your function not prompt [literally] for the phone number?) (Thought-provoker 2: Could your function prompt and avoid the problem(s) this causes?) Place the following sections of a typical C/C++ application in order by numbering the blanks. (Thought-provoker: Where would inline functions go?) _____ using namespace directive _____ #include's for libraries _______ function definitions _______ main function _______ prototypes (& global const's/typedef's) The ______ arguments appear in the function's head. They may be passed to the function via either the _______ mechanism or the _______ mechanism. The latter will accept a copy of the ________ argument (the one listed in the function call). The former will instead form a direct link to the memory location of the caller's argument - thus allowing the function to change that memory even though the function doesn't own it (i.e. that memory location isn't for one of the function's (global/local) variables/constants). Default arguments must be placed at the (left/right) end of the argument list. The default value specification should only be placed on the (first/second/last) function head the compiler sees. Therefore, they are generally placed in the ______ of a regular function or on the _______ of an inline function. TRUE/FALSE AU methods of a class can access the private data of the class. TRUE/FALSE Data which is public is generally considered normal when defining a class. TRUE/FALSE private methods, although rare, can often be useful for tasks the class must (or should) manage on its own