What guideline is violated if a public API uses exceptions for control flow?

What guideline is violated if a public API uses exceptions for control flow?

• A. G24 Overload with care
• B. G21 Don't force exceptions for control flow
• C. G13 Design/document for inheritance or prohibit it
• D. G9 Avoid overly clever APIs

Answer: (B)

Using exceptions for control flow in a public API violates the guideline which emphasizes not forcing exceptions for control flow. This principle is grounded in the idea that exceptions should be used for handling unusual or error circumstances rather than as a mechanism to control the standard flow of execution. When exceptions are used for normal control flow, it can lead to code that is difficult to read, maintain, and understand. Developers using the API might need to handle exceptions that arise in routine circumstances, which can lead to inefficiencies and complicate the logic of the application. This approach can also obscure the intention of the code, making it less clear what the normal operational pathway is and where exceptional situations truly occur. APIs are meant to be intuitive and facilitate straightforward interactions. Adhering to this guideline creates a more predictable and user-friendly experience for developers, encouraging them to utilize the API effectively without encountering unexpected exceptions in standard operations.

Using exceptions for control flow in a public API violates the guideline which emphasizes not forcing exceptions for control flow. This principle is grounded in the idea that exceptions should be used for handling unusual or error circumstances rather than as a mechanism to control the standard flow of execution.

When exceptions are used for normal control flow, it can lead to code that is difficult to read, maintain, and understand. Developers using the API might need to handle exceptions that arise in routine circumstances, which can lead to inefficiencies and complicate the logic of the application. This approach can also obscure the intention of the code, making it less clear what the normal operational pathway is and where exceptional situations truly occur.

APIs are meant to be intuitive and facilitate straightforward interactions. Adhering to this guideline creates a more predictable and user-friendly experience for developers, encouraging them to utilize the API effectively without encountering unexpected exceptions in standard operations.