What happens if you try to delete memory using the delete operator more than once?
- It gets deleted twice
- No effect
- Program crashes
- Memory gets duplicated
Deleting a memory location more than once leads to undefined behavior, most commonly resulting in program crashes. Always ensure memory is deleted once and pointers are set to nullptr afterwards.
In which year was the C++98 standard officially published?
- 1990
- 1995
- 1998
- 2002
The C++98 standard was officially published in 1998. It was the first standardized version of the C++ language, providing a foundation for many modern C++ features and establishing a baseline for future improvements.
What is the output of a function with a void return type?
- An integer
- A floating point number
- Nothing
- A character
In C++, a function declared with a void return type does not return any value. It is used when the function needs to perform an action but doesn't need to send any data back to the calling function.
Which of the following is a correct way to declare a function pointer in C++?
- int func()
- int *func()
- int (*func)()
- int &func()
In C++, a function pointer points to the address of a function. The correct syntax for declaring a function pointer is type (*pointer_name) (parameter list). In the given options, int (*func)() is the correct way to declare a function pointer returning an int.
What is the significance of the "default" case in a switch-case statement?
- It handles unspecified cases
- It serves as the primary case to be executed
- It is mandatory for all switch-case structures
- Acts as the else part in if-else structures
The "default" case in a switch-case statement is executed when none of the provided "case" conditions match the switch expression's value. It serves as a fallback and handles unspecified or unexpected values, ensuring that the switch has a response for all potential input. It is similar to the "else" in if-else.
The loop do { /* code */ } while(_______); will always execute the code block at least once.
- FALSE
- 1
- TRUE
- sometimes
The "do-while" loop in C++ always executes its body once before checking the condition. So even if the condition in the "while" part is "false", the body of the loop will execute once. This differentiates it from the "while" loop which checks the condition before the first execution.
Which of the following scenarios is most suitable for using a switch-case statement?
- When comparing string values.
- When there are many conditions that can occur in any order.
- When the conditions are based on a range of values.
- When dealing with enumerated values.
The switch-case structure in C++ is best suited for scenarios where a single variable's value needs to be checked against a series of constants, often seen with enumerated values. It's a cleaner and more readable alternative to a long series of if-else statements in such cases.
You are optimizing a recursive algorithm for a real-time system where function call overhead is a critical concern. What strategy might be most effective in reducing the function call overhead while maintaining the logical structure of the algorithm?
- Use inline functions.
- Optimize the algorithm's base cases.
- Introduce parallel processing.
- Rely on external libraries.
Function call overhead is the extra time and resources needed when a function is called. Using inline functions can help reduce this overhead, especially in recursive algorithms, because the function's code gets inserted (or "inlined") at each point where the function is called, eliminating the need for the typical call and return process, which can be resource-intensive.
The operator used to determine the remainder when one number is divided by another is _______.
- *
- %
- /
- +
In C++, the modulo operator % is used to determine the remainder of a division operation between two numbers. For example, 7 % 3 would yield a result of 1, as when 7 is divided by 3, the remainder is 1. It's a very useful operator, especially in situations that require calculations around loops and array indices.
When replacing nested if-else structures with a switch-case, what is a common pitfall to avoid?
- Ignoring the break statement
- Using non-integer values for cases
- Avoiding the default case
- Putting the default case at the beginning
When using switch-case statements, it's essential to remember to include the "break" statement at the end of each case. Without it, the program may execute subsequent cases, leading to unintended behavior known as "fall-through." The "break" statement ensures that once a match is found, no other cases are executed.