Programming Fundamentals

In PL/SQL, variables that are declared but not initialized default to NULL when execution begins. They do not default to 0, their default value does not depend on scale/precision, and they can still be used in the executable section.

GOTO provides unconditional transfer of control to a labeled section within a PL/SQL block, allowing immediate jump to a specific part without any condition. If-Then-Else requires condition evaluation, While loops execute based on a condition, and DECODE is a function for value substitution, not a control structure.

The Exception section (also called exception handler) is where user-defined and predefined exceptions are trapped and handled using WHEN clauses. The Declaration section declares variables and exceptions, the Execution section contains the main logic, and there is no 'Header' section in PL/SQL block structure.

System.exit() terminates the JVM immediately, preventing the finally block from executing. Additionally, the while(true) loop in the if branch never exits, so the finally block would never be reached in that case either. Only if neither branch executes would finally run, but the structure guarantees one of them does.

This is a duplicate of question 149704. System.exit() terminates the JVM immediately, preventing the finally block from executing. The while(true) loop also never exits. In both cases, the finally block is unreachable.

Static analysis examines code without executing it and can detect syntax errors, undeclared variables, type mismatches, and unreachable code. However, it cannot validate whether requirements are correctly captured or if the software meets user needs; requirements errors require manual review or dynamic testing. Options A, C, and D are all detectable through static code analysis.

Static analysis can detect structural issues like undefined variables (a), unreachable code (b), variable redefinitions (d), and array bounds violations (e) by analyzing code without execution. However, it cannot determine if a stored value is logically correct for the intended computation (c); that requires understanding requirements and dynamic testing.

Two test cases are sufficient for both statement and branch coverage. The first test (e.g., A=10, B=5, D=5) covers the true branch of the first IF and the true branch of the second IF. The second test (e.g., A=5, B=10, D=10) covers the false branches, achieving full coverage.

Static analysis examines code without executing it, so it can find structural issues like undefined variables, unreachable code, or variable redefinitions. However, it cannot verify semantic correctness - whether the value stored in a variable matches the intended business logic. Static analysis tools don't understand your requirements, so they can't tell if 'x = 5' should have been 'x = 10' - only dynamic testing with known inputs and expected outputs can verify correctness.

Black box techniques test software without examining internal code structure. Equivalence partitioning, state transition testing, and syntax testing are all black box techniques - they focus on inputs, outputs, and external behavior. LCSAJ (Linear Code Sequence and Jump) is a white box structural testing technique that requires analyzing code paths, branches, and control flow within the program's source code.

BS7925-II standard for software component testing defines white-box techniques as those examining internal structure like control flow, data flow, and statement coverage. Syntax testing is a black-box technique that validates input format against a grammar without considering internal code implementation. Random testing is also not a white-box technique, but syntax testing is more definitively a structural black-box method.

When a user-declared constructor is defined, the compiler stops generating the default constructor. This struct has two user-declared constructors: a copy constructor 'A(A& a)' and a converting constructor 'A(double d)'. Because at least one constructor is explicitly declared, the compiler will NOT generate any additional constructors (no default constructor, no copy constructor since one exists, no move constructors). Therefore, the number of implicitly-defined constructors is 0.

A function call is not always an rvalue in C/C++. Whether it's an rvalue depends on the return type - if a function returns by value, the call is an rvalue, but if it returns a reference, it can be an lvalue. For example, a function returning int& can be used as an lvalue.