Then, you simply add a #TRY/#CATCH block around your code:
\verbatim TRY{
/* your code */
-} CATCH(e) {
+}
+CATCH(e) {
/* error handling code */
} \endverbatim
Another strange thing is that you should actually free the memory allocated
to the exception with xbt_ex_fres() if you manage to deal with them. There
-is a bit more than this on the picture (#CLEANUP blocks, for example), and
-you should check the section \ref XBT_ex for more details.
+is a bit more than this on the picture (#TRY_CLEANUP blocks, for example), and
+you should check the section \ref XBT_ex for more details.
You should be <b>very carfull</b> when using the exceptions. They work great
when used correctly, but there is a few golden rules you should never break.
kill message to each ports of the search range. If it manage to close the
socket after sending the message without being interrupted by an exception,
it can assume that it killed the server and stop searching.
-\dontinclude 08-exceptions.c
+\don'tinclude 08-exceptions.c
\skip port=3000
\until end_of_loop
look like when it's not catched), we add a potential command line argument
to the server, asking it to cheat and to not open its port within the search
range but elsewhere:
-\dontinclude 08-exceptions.c
+\don'tinclude 08-exceptions.c
\skip strcmp
\until gras_socket_my_port
\until }
