跳到主要內容

Stringify C++ Enum Safely

Stringify Enum Safely

Sometimes stringifying C/C++ enumerator, or enum, values within its literal names are useful for debugging or logging. In this article, I’ll share how I achieve basic enum stringify and how to do it safely against changes to enum definitions.

Basic Idea

Given a boring enum Result as follows.

enum class Result : int8_t {
  OK = 0,
  FAILED,
};

My usual way to stringify them is using a table, i.e.

#define STR(X) #X
char const* StringifyResult(Result res) {
  char const* str[] = {
    STR(OK),
    STR(FAILED),
  };
  return str[static_cast<std::underlying_type_t<Result>>(res)];
}
int main() {
  printf("%s", StringifyResult(Result::OK)); // print "OK"
}

It benefits us from simplicity - simply copy’n paste those enum values then decorate them with STR(). Tons of editors can accomplish such editing in a snap.

Check Consistency

Occasionally we may change an enum definition - changes include adding, removal, and renaming. For first two cases, add a LAST enum value to end of an enum definition and static_assert the enum size. i.e.

#define STR(X) #X
enum class Result : int8_t {
  OK = 0,
  FAILED,
  LAST,
};
char const* StringifyResult(Result res) {
  char const* str[] = {
    STR(OK),
    STR(FAILED),
  };
  static_assert(Result::LAST == sizeof(str)/sizeof(char const*));
  // ...
}

In case of renaming, enhance the macro STR, to validate correct enum value names, with comma operator. i.e.

#define STR(Enum, X) ((void)Enum::X, #X)

Then apply the macro, e.g.

STR(Result, OK) // Expand as ((void)Result::OK, "OK")
  • The first operand, (void)Enum::X, of comma operator makes sure that the name X is a valid identifier of Enum and causes compile error if it’s not.
  • (void) suppresses compile warning/error of unused expression result.
  • If the first operand was compiled correctly, then #X is the final result of the comma expression.

Finally, whenever definition of an enum is changed, we get a compile error if the stringify function does not cover all enum values with valid names.


Written with StackEdit.

留言

這個網誌中的熱門文章

得利油漆色卡編碼方式

得利油漆色卡編碼方式 類似 Munsell 色彩系統 ,編碼方式為 HUE LRV/CHROMA 例如 10GY 61/449 ( 色卡 ) 編碼數值 描述 10GY hue ,色輪上從 Y(ellow) 到 G(reen) 區分為 0 ~ 99 ,數值越小越靠近 Y,越大越靠近 G 61 LRV (Light Reflectance Value) 塗料反射光源的比率,數值從 0% ~ 100% ,越高越亮,反之越暗,也可理解為明度 449 chroma 可理解為彩度,數值沒有上限,越高顏色純度 (濃度) 越高 取決於測量儀器,對應至 RGB 並不保證視覺感受相同。 參考資料: 色卡對照網站 e-paint.co.uk Written with StackEdit .

C++17 新功能 try_emplace

C++17 新功能 try_emplace 回顧 emplace 大家的好朋友 Standard Template Library (STL) 容器提供如 push_back , insert 等介面,讓我們塞東西進去; C++11 之後,新增了 emplace 系列的介面,如 std::vector::emplace_back , std::map::emplace 等,差異在於 emplace 是在容器內 in-place 直接建構新元素,而不像 push_back 在傳遞參數前建構,下面用實例來說明: struct Value { // ctor1 Value ( int size ) : array ( new char [ size ] ) , size ( size ) { printf ( "ctor1: %d\n" , size ) ; } // ctor2 Value ( const Value & v ) : array ( new char [ v . size ] ) , size ( v . size ) { printf ( "ctor2: %d\n" , size ) ; memcpy ( array . get ( ) , v . array . get ( ) , size ) ; } private : std :: unique_ptr < char [ ] > array ; int size = 0 ; } ; struct Value 定義了自訂建構子 (ctor1),以指定大小 size 配置陣列,複製建構子 (ctor2) 則會配置與來源相同大小及內容的陣列,為了方便觀察加了一些 printf 。當我們如下使用 std::vector::push_back 時 std :: vector < Value > v ; v . push_back ( Value ( 2048 ) ) ; 首先 Value 會先呼叫 ctor1,傳給 push_ba...

Notes for C/C++ Programming

Notes for C/C++ Programming Notes for C/C++ Programming Off by One Error Prone # define LEN 128 char buf [ LEN ] = { 0 } ; // -1 for prevent missing NULL terminator // since strncpy doesn't preserve it for us. strncpy ( buf , something , sizeof ( buf ) - 1 ) ; // snprintf does preserve NULL terminator for us // i.e. actual size for placing characters is sizeof(buf) - 1 // but it takes extra time to parsing format snprintf ( buf , sizeof ( buf ) , something ) ; Bad things often happen when we mess with -1 or +1 to pointers point to continuous elements. Absorber # define LEN 128 char buf [ LEN + 1 ] = { 0 } ; // ^^^^ Always preserve 1 byte strncpy ( buf , somethin , sizeof ( buf ) ) ; Constant Correctness (C/C++) Bad void do_something ( char * dest , char * src ) ; struct MyList { void do_something ( std :: string & name ) ; } ; Reason : Will the name be modified by the lookup method? Will stat...