Changes between Version 1 and Version 2 of HowToIfortTraceback

Timestamp:

Dec 9, 2008, 8:18:32 PM (15 years ago)

Author:

gallmei

Comment:

--

HowToIfortTraceback

@@ -12 +12 @@
 }}}
 
-It is possible to use the same machinery for your own programmer purposes:
+It is possible to use the same machinery for your own programmer purposes.[[BR]]
+It is also possible, to emit an error message just as a warning and return to the calling routines.
+
+See also: Ifort documentation, TraceBackQQ
+
+
+----
+'''Using GiBUU:'''
+
+Insert at the beginning of your module:
+{{{
+    USE CallStack
+}}}
+and at the position, where you want to get the error message:
+{{{
+    call TRACEBACK([string],[user_exit_code])
+}}}
+
+The both optional arguments are:
+
+ * ''string'': Text to be written
+ * ''user_exit_code'':  By specifying a user exit code of -1, control returns to the calling program. Specifying a user exit 
+   code with a positive value requests that specified value be returned to the operating system. The default 
+   value is 0, which causes the application to abort execution.
+
+If you are not compiling with ifort: the behavior of the module stays the same, just without printing the call stack; text is written or not, code stops or not.
+
+----
+'''In General:'''
 
 
@@ -24 +52 @@
 }}}
 
-It is also possible, to emit an error message just as a warning and return to the calling routines.
-
-See also: Ifort documentation, TraceBackQQ