Using @c printf or @c println to display information is possible, but
quickly unpractical, as the logs of all processes get intermixed in
-your program's output. %As an answer, the SimGrid logging module allow
+your program's output. As an answer, the SimGrid logging module allow
you to sort and filter the logs by emitter, by module and by gravity
level.
- %%L: line number where the log event was raised (LOG4J compatible)
- %%M: function name (LOG4J compatible -- called method name here of course).
- - %%b: full backtrace (Called %%throwable in LOG4J).
- Defined only under windows or when using the GNU libc because backtrace() is not defined
- elsewhere, and we only have a fallback for windows boxes, not mac ones for example.
- - %%B: short backtrace (only the first line of the %%b).
- Called %%throwable{short} in LOG4J; defined where %%b is.
-
- %%d: date (UNIX-like epoch)
- %%r: application age (time elapsed since the beginning of the application)
@subsubsection log_use_conf_add Category additivity
-The <tt>add</tt> keyword allows to specify the additivity of a
+The <tt>add</tt> keyword allows one to specify the additivity of a
category (see @ref log_in_app). '0', '1', 'no', 'yes', 'on'
and 'off' are all valid values, with 'yes' as default.
The default appender function currently prints to stderr.
-*/
\ No newline at end of file
+*/
