summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohnny Willemsen <jwillemsen@remedy.nl>2020-08-26 16:15:22 +0200
committerJohnny Willemsen <jwillemsen@remedy.nl>2020-08-26 16:15:22 +0200
commitdac841ab98249ba3984f7cae975115d0f3ad236e (patch)
tree252f2ea9f965dfb3ad4659490b390d329265e9be
parent8b02c0495ec5d3fae0ab8de6985701337eb8eec6 (diff)
downloadATCD-dac841ab98249ba3984f7cae975115d0f3ad236e.tar.gz
Indent change in class docu
* ACE/ace/Log_Msg_Callback.h:
-rw-r--r--ACE/ace/Log_Msg_Callback.h38
1 files changed, 19 insertions, 19 deletions
diff --git a/ACE/ace/Log_Msg_Callback.h b/ACE/ace/Log_Msg_Callback.h
index 0493a076933..f61587013ee 100644
--- a/ACE/ace/Log_Msg_Callback.h
+++ b/ACE/ace/Log_Msg_Callback.h
@@ -27,27 +27,27 @@ class ACE_Log_Record;
*
* @brief An interface class used to get logging callbacks.
*
- * Users who are interested in getting the logging messages
- * directly, can subclass this interface and override the log()
- * method. They must then register their subclass with the
- * Log_Msg class and make sure that they turn on the
- * ACE_Log_Msg::MSG_CALLBACK flag.
+ * Users who are interested in getting the logging messages
+ * directly, can subclass this interface and override the log()
+ * method. They must then register their subclass with the
+ * Log_Msg class and make sure that they turn on the
+ * ACE_Log_Msg::MSG_CALLBACK flag.
*
- * Your log() routine is called with an instance of
- * ACE_Log_Record. From this class, you can get the log
- * message, the verbose log message, message type, message
- * priority, and so on.
+ * Your log() routine is called with an instance of
+ * ACE_Log_Record. From this class, you can get the log
+ * message, the verbose log message, message type, message
+ * priority, and so on.
*
- * Remember that there is one Log_Msg object per thread.
- * Therefore, you may need to register your callback object with
- * many ACE_Log_Msg objects (and have the correct
- * synchronization in the log() method) or have a separate
- * callback object per Log_Msg object. Moreover,
- * ACE_Log_Msg_Callbacks are not inherited when a new thread
- * is spawned because it might have been allocated off of the
- * stack of the original thread, in which case all hell would
- * break loose... Therefore, you'll need to reset these in each
- * new thread.
+ * Remember that there is one Log_Msg object per thread.
+ * Therefore, you may need to register your callback object with
+ * many ACE_Log_Msg objects (and have the correct
+ * synchronization in the log() method) or have a separate
+ * callback object per Log_Msg object. Moreover,
+ * ACE_Log_Msg_Callbacks are not inherited when a new thread
+ * is spawned because it might have been allocated off of the
+ * stack of the original thread, in which case all hell would
+ * break loose... Therefore, you'll need to reset these in each
+ * new thread.
*/
class ACE_Export ACE_Log_Msg_Callback
{