Changes between Version 5 and Version 6 of code/Error_handling

Timestamp:

Apr 12, 2017, 10:15:42 PM (7 years ago)

Author:

landauf

Comment:

fixed links

code/Error_handling

@@ -1 +1 @@
 = Error handling in Orxonox =
-[[TracNav(TracNav/TOC_Development)]]
 
 Whenever something unwanted happens, the programmer needs to react in a certain way.[[br]]
@@ -10 +9 @@
 
 == orxout(#), displays messages ==
-Whenever you want to show the user or the programmer a message, use orxout(#) where # is the level of your output. See [wiki:Output] for more information. [[br]]
+Whenever you want to show the user or the programmer a message, use orxout(#) where # is the level of your output. See [wiki:doc/Output] for more information. [[br]]
 
 '''Note: A simple message with level user_error (or internal_error) doesn't trigger an exception or anything yet'''
@@ -16 +15 @@
 == Exceptions ==
 This kind of error handling method is used when the programmer has to handle situations that could go wrong, but shouldn't. Mind the difference to Assertions below! [[br]]
-For information about how to use them, see [wiki:Exception Exceptions]. [[br]]
+For information about how to use them, see [wiki:doc/Exception Exceptions]. [[br]]
 A good example for exceptions would be a script compiler. Whenever it encounters bad tokens, it throws an exception with a message. The function calling the parser can then catch that exception, display it and act accordingly. [[br]]
 We also use Exceptions when loading a level. If one occurs, we can abort and the user can choose another level. Of course this shouldn't happen, but nobody's perfect. [[br]][[br]]
@@ -39 +38 @@
 '''Important: Asserts are only useful when the mistake is in the program. Throwing asserts for bad input doesn't help anyone, use exceptions then! [[br]]
 
-Usage: 'assert(condition you assume);' or when you want to tell more use 'OrxAssert(condition, message)'. The message gets then displayed via orxout(user_error) before the assert() macro is called. [[br]]
+Usage: 'assert(condition you assume);' or when you want to tell more use '!OrxAssert(condition, message)'. The message gets then displayed via orxout(user_error) before the assert() macro is called. [[br]]
 The example above would then read: