Anonymous user
Talk:Assertions: Difference between revisions
→Boolean expression?: Missing mention of a test in the task description
m (Typo error) |
(→Boolean expression?: Missing mention of a test in the task description) |
||
Line 3:
:: If you've got a managed monitoring environment, the only way that the program might see the assertion failure might be as a very long time to execute some piece of code. (There are many different ways to handle an assertion failure trap; throwing a normal exception is only one of them.) —[[User:Dkf|Donal Fellows]] 09:30, 26 October 2009 (UTC)
::: The program may not see an assertion failure in itself. Another program (e.g. the debugger, watch dog monitor, OS supervisor etc) can. The problem with assertions in many implementations is that they execute code with side effects on the program context. It is important for this task to specify whether the language implementation of assertions is consistent in not violating the program semantics, e.g. in having no side effects whenever assertions enabled or disabled. --[[User:Dmitry-kazakov|Dmitry-kazakov]] 19:49, 26 October 2009 (UTC)
==Boolean expression?==
The task description fails to mention that assertions test some expression that is expected to be true for normal program flow to continue. This aspect is also mentioned [[wp:Assertion (computing)|here]] on wp. Shouldn't the task description be modified? --[[User:Paddy3118|Paddy3118]] 09:49, 24 March 2010 (UTC)
| |||