MFC and Java Programming Quiz

The code compiles and runs. Byte b is not explicitly initialized but gets value from final int x (which is compile-time constant 10). Since 10 fits in byte range (-128 to 127), the assignment is valid. Output is 10.

Option B Float.isNan(x) is the correct approach for checking NaN. Option A x == Float.NaN is always false because NaN is not equal to anything including itself (IEEE 754 rule). Option C depends on MyObject's equals implementation - most objects won't handle NaN comparison correctly. B is the only valid answer.

The Java assertion statement syntax requires the second expression (after the colon) to return a value. Because methodB() has a void return type, it cannot be used as the detail message expression, causing a compilation error.

The instanceof operator checks if an object is an instance of a specific type or interface. MyInstanceTest implements MyInterface, so 't instanceof MyInterface' returns true (prints 'I am true interface'). The static variable 's' is null (default value), and 'null instanceof String' returns false (prints 'I am false String'). The instanceof operator safely handles null values by returning false instead of throwing an exception.

The ternary operator expression ((a < 5) ? 9.9 : 9) involves type promotion. Since the second operand (9.9) is a double, the third operand (9) is promoted to double, and the result is 9.0 (not 9). The output is 'Value is - 9.0', which doesn't match option A (9), B (5), or C (compilation error). Therefore D (None of these) is correct. This tests understanding of numeric promotion in ternary expressions.

myThread overrides start(), so calling myThread.start() executes its custom method, printing 'MyThread: start()'. thread is initialized with myRunnable, so calling thread.start() executes myRunnable.run(), printing 'MyRunnable: run()'.

Initially, static variable x is 0. x-- decrements it to -1. In myMethod(), y = x++ + ++x evaluates as -1 + 1 = 0, leaving x at 1. Back in main, x + y + ++x evaluates to 1 + 0 + 2 = 3.

Java passes object references by value. In second(), the local parameter 'v' is reassigned to a new Value object (v = val), which doesn't affect the original reference in first(). However, before reassignment, v.i = 20 modifies the object's field through the original reference. The second() method prints '15 0' (val.i=15, local i=0). Back in first(), v.i is 20 (modified by second() before reassignment), so it prints '20'. Final output: '15 0 20'. The reassignment in second() doesn't affect first()'s reference.

The code compiles and runs successfully. myChi.addMe(10, 20, 30) returns 10 + 10 + 20 + 20 + 30 + 30 = 120. myChi.addMe(myChi) calls addMe(10, 20, 30) on itself, returning 120. myPar.addMe(myPar) returns 10 + 10 + 20 + 20 = 60. The sum is 120 + 120 + 60 = 300.

The nested if structure is: if(a) { if(b) { if(c) {...} else {...} } else if(a && (b=c)) {...} else {...} }. With a=true, b=false, c=true: The outer if(a==true) succeeds. Inside, if(b==true) fails (b is false), so we go to else if(a && (b=c)). Here, (b=c) assigns c to b, making b=true, so the condition (true && true) is true, printing "It's too confusing to tell what is true and what is false". This output is not listed in options A, B, or C, so D is correct.

The code compiles successfully. SubclassY extends SuperclassX (protected method, package-private field) from packageX.packageY - subclasses can access protected members. Line 5 is valid (polymorphism: SubclassY IS-A SuperclassX). Lines 9-11 access protected method and package-private field through a SubclassY reference, which is valid within the same package hierarchy. The code compiles and runs without errors, so 'None of these' (D) is correct.

The code creates two separate String objects using 'new String("Test")'. The == operator compares object references, which are different for distinct objects, so s1==s2 is false. The equals() method compares string content, and both strings contain 'Test', so s1.equals(s2) is true. The code prints only 'Equals'. This tests the fundamental distinction between reference equality (==) and content equality (equals()).

In Java, String objects are immutable. Calling str.concat("Bangalore") creates a new String object containing "TCSBangalore", but it does not modify the original reference str. Therefore, str remains "TCS".

CDC (Device Context) class in MFC provides member functions for device-context operations including drawing tools selection, GDI object management, and color/palette operations. It's the fundamental class for all drawing operations in Windows. CBrush handles only brush objects, CAnimateCtrl is for animation controls, and CDOCItem is for document items.

A Map is a collection data structure designed to associate unique key objects with corresponding value objects, allowing efficient retrieval of values based on their keys.

CObject provides serialization support through the Serialize method, runtime class information via DECLARE_DYNAMIC/IMPLEMENT_DYNAMIC macros, and diagnostic dumping through Dump. Platform independence is not a feature - CObject is part of Windows-specific MFC.

The MFC library wraps the Windows HMENU handle and provides menu management functionality through the CMenu class. Thus, the statement is true.

An MFC application must have exactly one unique object of a class derived from CWinApp. Having multiple CWinApp objects in a single application is not allowed.

CPropertyPage is the class for property sheet pages in MFC and is declared in afxdlgs.h, which contains common dialog classes including property sheets/pages.

MFC's message map mechanism connects windows messages and command IDs to member functions using macros like BEGIN_MESSAGE_MAP and ON_COMMAND, avoiding the need for a giant switch statement.