Multiple Programming Languages Quiz

COBOL-85 was the version where the GO TO statement was eliminated from the standards. Earlier versions (68, 74) still included GO TO, and COBOL-9x maintained this structured programming approach without GO TO.

In SAP ABAP Dictionary, the 'Data Browser/Table View Maintenance' setting (such as 'Display/Maintenance Allowed') regulates whether and how users can view, edit, or maintain the table's records using tools like SE16 or SM30.

In ABAP, the two elementary types for character strings are 'c' (text fields for character data) and 'n' (numeric text fields for strings of digits used for formatting without arithmetic). Options a/b, x/y, and p/f represent different ABAP data types.

In ABAP, Type F (floating point) cannot be used to define parameters in FORM/PERFORM statements, whereas Types C (character), N (numeric character), and P (packed) are valid parameter types.

In ABAP, CONSTANTS declarations must include a VALUE clause to specify the constant's value. Option C 'Constants:x(3) type c.' lacks the required VALUE clause, causing a syntax error. DATA statements (options B and D) can optionally include values, so they are syntactically valid.

When CLEAR is used on an internal table without a header line, it initializes all lines of the table body to their initial values. This is different from tables with header lines, where CLEAR might only initialize the header work area. Option C correctly states that all lines are initialized.

The SQL%ROWCOUNT attribute returns the number of rows affected by the last SQL statement. If the DELETE statement did not find any matching rows to delete, SQL%ROWCOUNT returns 0.

The WHERE clause 'WHERE sal, bonus IN' is syntactically incorrect. When using multiple columns with the IN operator in SQL, you must use row value constructor syntax like 'WHERE (sal, bonus) IN (SELECT sal, bonus FROM...)'. The comma-separated form without parentheses is not valid SQL syntax.

The WHERE CURRENT OF clause requires that the cursor was declared with a FOR UPDATE clause. This clause locks the rows that will be updated or deleted, ensuring that the data hasn't changed between when the cursor was opened and when the position-based operation occurs. Without FOR UPDATE, the database cannot guarantee data integrity for the positioned operation.

PL/SQL cursors can accept parameters, making them reusable with different values each time they're opened. Parameterized cursors allow you to write the cursor definition once and open it multiple times with different parameter values, avoiding code duplication.

In C++, a function prototype is only required if the function is called before it is defined in the file. If the complete function definition appears before the first function call, the definition itself serves as the declaration. The compiler can determine the function's signature from its definition.

In C++, when calling a function with default parameters, you cannot skip an earlier parameter while providing a value for a later parameter. If you want to specify the second parameter, you must also provide a value for the first parameter. The syntax 'func(,4)' is invalid because it omits the first argument.

Public inheritance in object-oriented programming represents an 'is-a' relationship. A derived class publicly inheriting from a base class should be able to substitute for the base class (Liskov Substitution Principle). For example, if 'Car' inherits publicly from 'Vehicle', a Car IS-A Vehicle. This is in contrast to composition, which represents a 'has-a' relationship.

A const pointer (pointer to const data) cannot be implicitly assigned to an ordinary (non-const) pointer because this would allow modification of data that was declared as constant. This would violate the const-correctness principle of C++. You would need an explicit const_cast to perform this conversion, and even then, modifying the data through the resulting pointer is undefined behavior.

The CREATE SYNONYM statement without the PUBLIC keyword creates a private synonym that only Carl (the creator) and Stanley (the object owner) can access. Since 'PUBLIC' was not specified, this is a private synonym, not a public one. Option A is incorrect because Stanley can also access it, option B is incorrect because it's private, option C is incorrect because synonym names can match object names, and option E is incorrect because this is a local synonym.

The invalid statements are: SELECT lname, jobid, sal FROM emp (sal + 500); due to incorrect parenthesis syntax; SELECT lname, jobid, sal, sal + 500 bonus FROM emp due to a missing semicolon; and SELECT lname, sal + 500 Employee Bonus FROM emp; because multi-word aliases require double quotes.

This is a self join because the emp table is joined to itself using two different aliases (a and b). A self join is used when a table needs to be compared with itself, such as finding relationships between rows in the same table. The WHERE clause a.empid=b.empid creates an equijoin condition (using equality), but the defining characteristic is that it's a self join. The statement is syntactically valid and will execute successfully, returning each employee's lname and location paired with their dname and hiredate from the same row.

The variable var1 is declared as a CONSTANT in the PL/SQL block. Constants cannot have their values reassigned after initialization. The line var1 := var2 + 2000; attempts to modify this constant, which triggers a compilation error.