Programming Languages Fundamentals

toString() is defined in the Object class and inherited by all classes including String. String overrides toString() but does not originate it.

JavaBeans are simple reusable components with properties and methods. They are not J2EE components like EJBs, servlets, or JSPs which are part of the enterprise framework.

The Math class has a private constructor and all its methods are static. You cannot create instances of utility classes in Java.

The sum is 100+10+20 = 130. Integer division 130/3 yields 43 (truncates toward zero). This integer is stored in float variable as 43.0, then printf with %.2f format shows 'ave= 43.00'. Option B is wrong because it shows 43.33, which would require floating-point division (130.0/3).

In C++, constructors cannot be declared with the const cv-qualifier. Attempting to declare a constructor as const results in a compile-time error because constructors are meant to initialize and modify non-const objects.

In C, function arguments are evaluated from right to left in many compilers (like GCC). Evaluating x=x>>2 first shifts 5 right by 2, making x equal to 1. Then x<<2 evaluates to 4, and the final x is 1, resulting in '1 4 1'.

The assignment a=1 sets a to 1 and returns 1, which is truthy. The ternary operator ? therefore evaluates to 2, assigned to b. printf outputs '1 2'. Option A (1 3) would be the result if the assignment returned 0 (falsey).

Tracing the pointers: abc.next points to def, def.next points to ghi, ghi.prev points back to def, def.next points to ghi, and ghi.i equals 2. The entire expression evaluates to 2. Option A (1) would be def.i, and Option C (3) would be jkl.i.

The function sets the register variable _AX to 1000. In many C compilers (especially older ones like Turbo C), return values are passed through the _AX register. When abc() is called, it sets _AX=1000, and main retrieves this as the return value i.

In C++, new int(87) allocates memory for a single int and initializes it to 87. The pointer p points to this allocated int containing value 87. Option D would require new int[87] (array syntax).

reinterpret_cast is used for low-level reinterpreting of bit patterns between inherently incompatible pointer types (e.g., int* to char*). static_cast is for related types, dynamic_cast for polymorphic downcasting, and const_cast for removing const/volatile.

When a derived class inherits a virtual function, it remains virtual in the derived class. This enables polymorphism - a base pointer can call the correct overridden function at runtime. This is fundamental to C++ polymorphism.

FLOW-MATIC, COBOL, and COMTRAN were all business-oriented programming languages developed for data processing. Pascal was primarily designed as a general-purpose and educational language, not for business systems.

COBOL inherited its four-division structure (IDENTIFICATION, ENVIRONMENT, DATA, and PROCEDURE) from FLOW-MATIC. Option A correctly lists three of these core divisions - the procedural, data definition, and environment setup divisions.

CODASYL was the committee that CREATED and DEVELOPED COBOL standards, not an approval body. ANSI (American National Standards Institute), USASI (United States of America Standards Institute), and ASI were standards organizations that APPROVED COBOL standards.

COBOL-68 was the first version of COBOL to be standardized by ANSI (and subsequently approved by ISO), establishing a baseline standard for the programming language across different hardware systems.

The PICTURE clause (for data formatting and editing) in COBOL was borrowed from COMTRAN (Commercial Translator), not from FLOW-MATIC, FORTRAN, or Pascal. COMTRAN was an IBM business language that contributed this data description feature.

When the CODASYL committee first named the language in 1959, they called it 'Common Business Language' (CBL). It was later renamed to COBOL (Common Business Oriented Language). Option B reflects this original name.

The first version of COBOL was released in 1958. This was when CODASYL completed the initial specifications. 1960 saw wider adoption, and later versions (68, 74, 85) came in subsequent decades.

After COBOL-85, the CODASYL committee and the X3J4 (ANSI COBOL committee) merged to form the existing J4 committee. This consolidation unified the development and standardization efforts under a single committee.