ALLOW_ASSERT_DIALOG¶
Description¶
When enabled, assertion failures will display dialog boxes for immediate developer attention.
Type¶
Boolean yes/no, on/off, 1/0
When to Enable¶
During Development and Testing: This allows developers to see assertion failures immediately.
Desktop/Interactive Applications: The user can interact with the dialog box and report the issue.
When to Disable¶
Server Environments: There is no user to interact with the dialog box. This is especially true for headless system where there is no display or user interface.
Automated Testing/Batch Jobs: The test cannot interact with a dialog box.
Production Environments: The dialog box would disrupt service.
Embedded Systems: There is no user to interact with the dialog box.
Multi-user Environments: The dialog box would disrupt the program flow.
Error Handling Strategy¶
When the dialog is disabled, the application should have a fallback error handling strategy in place. This could be a log file, a message to the user, or a simple error message. For production environments, the application should be able to continue running after the assertion failure.