Match the name of the constructor in the first column to its description from th

Question

Match the name of the constructor in the first column to its description from the second column. Why don't class input methods typically display a prompt for the user? Shouldn't the program always prompt before input? When writing a library. we place preprocessor directives in the interface file. What problem(s) are we trying to alleviate with these three preprocessor directives? Given functions with the purposes on the left. indicate which of the libraries on the right you would place each into by writing its letter in the blank next to the library 'title'. If none of the libraries seems right to you. you may 'create' your own in the extra spaces provided - but think carefully before you decide to do so. (And do NOT suggest a standard library!)

Explanation / Answer

27)

A==>2

B==>3`

C==>1

28)

Whenever a extrnal[user input not generated by program or not hard coded in program] input is to be taken we prompt user for values
so that program can proceed with valid data which is taken from user in consol during runtime
for eg
scanf in C programming
scanner class in Java

before taking input the user gets a command displayed on consol using print statement so that user understand for what he is putting value

print statment not necessary but it is best practice for better understanding about the "input"

29)

First we will know what is interface files:
The interface file (also called as a header file) tells other programs or libraries what facilities are available from this library.
It is like a menu that others can choose from to know what constants, type definitions, and functions this library is making available to them.

Typically only constants, typedef's, and function prototypes
would be found in an interface file.

As complex libraries will often include other libraries and it is possible for such a structure as:
lib A-->lib B--> lib C--> lib A
here lib A is having B which is having lib C and C is having lib A

this leads to a loop which calling each library to stop this loop we place some other preprocessor directives in the interface file to force the compiler to remember that it has seen that header file before and make it realize that it need not include it again. These directives are fashioned like:

#ifndef _____SYMBOL_UNIQUE_TO_THIS_LIBRARY______
#define _____SYMBOL_UNIQUE_TO_THIS_LIBRARY______

// constants, typedef's, and function prototypes

#endif

30)

A point library

B,F,J random library

G,H i/o library

H Curses library-->The Curses library is designed for working with the console in C.

C,D,E,I math library

Related Questions

Navigate

• Browse (All)
• Browse M
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.