TCS Papers: Sample Questions 175 - 176 of 502

Examrace Placement Series prepares you for the toughest placement exams to top companies.

Question number: 175

» Languages » C & C Plus Plus

Short Answer Question▾

Write in Short

Can include files be nested?

Explanation

  • Yes.

  • Include files can be nested any number of times.

  • However, same files should not be included twice.

  • Many of today’s popular compilers make up for this difficulty by implementing a concept called precompiled headers, in which all headers and associated dependencies are stored in a precompiled state.

  • Many programmers like to create a custom header file that has #include statements for every header needed for each module. This can help avoid potential problems relating to #include files, such as accidentally omitting a #include file in a module.

Question number: 176

» Languages » Assembly Language

Essay Question▾

Describe in Detail

What is Assembly Manifest?

Explanation

Assemblies maintain all their information in a special unit called the manifest. Followings are the contents of an Assembly Manifest:

  • Assembly name: Represents text string specifying the assembly’s name.

  • Version number: Represents major and minor version number, as well as a revision and build number. The CLR makes use of these numbers to enforce version policy.

  • Culture: Represents information of the culture or language, which the assembly supports. An assembly is a container of only resources containing culture- or language-specific information.

  • Strong name information: Represents the public key from the publisher, if a strong name is assigned to an assembly.

  • List of all files in the assembly: Represents a hash of each file contained in the assembly and a file name.

  • Type reference information: Represents the information used at the runtime to map a type reference to the file that contains its declaration and implementation.

  • Information on referenced assemblies: Represents a list of other assemblies statically referenced by the assembly. Each reference includes the names of dependent assemblies, assembly metadata (version, culture, operating system, and so on), and public key, if the assembly is strong named.