Changeset 372 for cpp/common/hmessage.h

Timestamp:

04/22/15 04:14:59 (10 years ago)

Author:

sz

Message:

Renamed some classes and functions to make their purpose more obvious:

• FramMessage?, FMprintf, etc. become Hmessage, Hprintf, etc... (H for handled message).
• ErrorManager? (and its family) becomes MessageHandler?. Handler names reflect their function better, e.g. MessageHandlerToStdout?.

All MessageHandlers? must now be given the explicit "Enable" argument if you want them to automatically become active. This makes side effects clearly visible.

File:

• cpp/common/hmessage.h (moved) (moved from cpp/common/framsg.h) (1 diff)

cpp/common/hmessage.h

@@ -3 +3 @@
 // See LICENSE.txt for details.
 
-#ifndef _FRAMSG_H_
-#define _FRAMSG_H_
+#ifndef _HMESSAGE_H_
+#define _HMESSAGE_H_
 
 #include <stdarg.h>
 
-extern const char* MSG_LEVEL[];
-#define FRAMSG_FORMAT "%s%s.%s: %s"
-#define FRAMSG_MULTILINE_CONTINUATION "..."
+extern const char* HMSG_LEVEL[];
+#define HMSG_FORMAT "%s%s.%s: %s"
+#define HMSG_MULTILINE_CONTINUATION "..."
 
-void FMprintf(const char *o,const char *m,int w,const char *bl, ...);
-void FMprintf_va(const char *o,const char *m,int w,const char *bl,va_list va); //a different name than FMprintf - otherwise the compiler could confuse the "string" parameter with va_list and could call the wrong function
-void printFM(const char *bl,...); //a shorthand for printf (a different name again to avoid the risk of confusion with the two functions above. This would be unlikely but possible when the argument types would match)
-void FramMessage(const char *o,const char *m,const char *txt,int w);
+void Hprintf(const char *o,const char *m,int w,const char *bl, ...);
+void Hprintf_va(const char *o,const char *m,int w,const char *bl,va_list va); //a different name than Hprintf - otherwise the compiler could confuse the "string" parameter with va_list and could call the wrong function
+void printH(const char *bl,...); //a shorthand for printf (a different name again to avoid the risk of confusion with the two functions above. This would be unlikely but possible when the argument types would match)
+void Hmessage(const char *o,const char *m,const char *txt,int w);
 
-void _FramMessageSingleLine(const char *o,const char *m,const char *txt,int w); //don't call this directly - it is used internally
+void _HmessageSingleLine(const char *o,const char *m,const char *txt,int w); //don't call this directly - it is used internally
 
-#define FMLV_DEBUG -1
-#define FMLV_INFO 0
-#define FMLV_WARN 1
-#define FMLV_ERROR 2
-#define FMLV_CRITICAL 3
+#define HMLV_DEBUG -1
+#define HMLV_INFO 0
+#define HMLV_WARN 1
+#define HMLV_ERROR 2
+#define HMLV_CRITICAL 3
 
 /*