Artefact:Model/com/sphenon/basics/exception/ExceptionVerificationFailure - Revision history

AndreasLeue at 13:07, 26 March 2010

2010-03-26T13:07:00Z

← Older revision		Revision as of 13:07, 26 March 2010
Line 27:		Line 27:
	cause or location of the error.		cause or location of the error.

	~~<span style="color:#800000;">~~'''Caution:'''~~</span>~~		'''Caution:'''
	Checks throwing these exceptions can typically be disabled for		Checks throwing these exceptions can typically be disabled for
	production releases after sufficient testing. In fact, you are		production releases after sufficient testing. In fact, you are
Line 33:		Line 33:
	user input validation or similar purposes.		user input validation or similar purposes.

	~~<span style="color:#800000;">~~'''Important:'''~~</span>~~		'''Important:'''
	Though it might be tempting to use this class of exceptions		Though it might be tempting to use this class of exceptions
	- specifically the subclass [[Artefact:Model/com/sphenon/basics/exception/ExceptionAssertionProvedFalse\|ExceptionAssertionProvedFalse]] -		- specifically the subclass [[Artefact:Model/com/sphenon/basics/exception/ExceptionAssertionProvedFalse\|ExceptionAssertionProvedFalse]] -

AndreasLeue at 10:01, 26 March 2010

2010-03-26T10:01:16Z

← Older revision		Revision as of 10:01, 26 March 2010
Line 35:		Line 35:
	<span style="color:#800000;">'''Important:'''</span>		<span style="color:#800000;">'''Important:'''</span>
	Though it might be tempting to use this class of exceptions		Though it might be tempting to use this class of exceptions
	- specifically the subclass [[Artefact:Model/com/sphenon/basics/~~exceptions~~/ExceptionAssertionProvedFalse\|ExceptionAssertionProvedFalse]] -		- specifically the subclass [[Artefact:Model/com/sphenon/basics/exception/ExceptionAssertionProvedFalse\|ExceptionAssertionProvedFalse]] -
	for each and every purpose, to avoid the effort of choosing		for each and every purpose, to avoid the effort of choosing
	an appropriate classification, don't take the bait. Firstly, these		an appropriate classification, don't take the bait. Firstly, these
	checks might be disabled, as mentioned, and secondly, software		checks might be disabled, as mentioned, and secondly, software
	quality depends utterly on useful problem reporting.		quality depends utterly on useful problem reporting.

AndreasLeue: New page: {{Metabox | Meta_Type = Type:org/oomodels/WIML/1.0 | Meta_Domain = Domain:it/test | Meta_Category = Type:org/oomodels/wiki/Model | Meta_Downloa...

2010-03-26T09:48:26Z

New page: {{Metabox | Meta_Type = Type:org/oomodels/WIML/1.0 | Meta_Domain = Domain:it/test | Meta_Category = Type:org/oomodels/wiki/Model | Meta_Downloa...

New page

{{Metabox
| Meta_Type = Type:org/oomodels/WIML/1.0
| Meta_Domain = Domain:it/test
| Meta_Category = Type:org/oomodels/wiki/Model
| Meta_Download = true
| Meta_Diagram = Artefact:Diagram/com/sphenon/basics/exception/Exceptions
| Meta_AddTypeToCategory = true
| Meta_AddCategoryToCategory = true
}}

== Code ==

<wiml>
* ExceptionVerificationFailure
> com/sphenon/basics/exception/ExceptionError
</wiml>

== Description ==

A safety check failed. I.e., a check, added for verfication
purposes, proved false. Obviously, in normal operation, such errors are
not supposed to occur. Therefore the actual reason is unknown, since
otherwise it could have been avoided.

The occurence of these failures typically indicate a programming
error. The various subclasses provide more information on the presumed
cause or location of the error.

<span style="color:#800000;">'''Caution:'''</span>
Checks throwing these exceptions can typically be disabled for
production releases after sufficient testing. In fact, you are
encouraged to do this. Therefore: do not use these exceptions for
user input validation or similar purposes.

<span style="color:#800000;">'''Important:'''</span>
Though it might be tempting to use this class of exceptions
- specifically the subclass [[Artefact:Model/com/sphenon/basics/exceptions/ExceptionAssertionProvedFalse|ExceptionAssertionProvedFalse]] -
for each and every purpose, to avoid the effort of choosing
an appropriate classification, don't take the bait. Firstly, these
checks might be disabled, as mentioned, and secondly, software
quality depends utterly on useful problem reporting.