[cpplint] reported by reviewdog 🐶 Almost always, snprintf is better than strcat [runtime/printf] [4] Raw Output: src/cjit.c:250: Almost always, snprintf is better than strcat [runtime/printf] [4]

[cpplint] reported by reviewdog 🐶 Complex multi-line /*...*/-style comment found. Lint may give bogus warnings. Consider replacing these with //-style comments, with #if 0...#endif, or with more clearly structured multi-line comments. [readability/multiline_comment] [5] Raw Output: src/kilo.c:88: Complex multi-line /*...*/-style comment found. Lint may give bogus warnings. Consider replacing these with //-style comments, with #if 0...#endif, or with more clearly structured multi-line comments. [readability/multiline_comment] [5]

[cpplint] reported by reviewdog 🐶 Empty loop bodies should use {} or continue [whitespace/empty_loop_body] [5] Raw Output: src/kilo.c:287: Empty loop bodies should use {} or continue [whitespace/empty_loop_body] [5]

[cpplint] reported by reviewdog 🐶 If you can, use sizeof(seq) instead of 32 as the 2nd arg to snprintf. [runtime/printf] [3] Raw Output: src/kilo.c:380: If you can, use sizeof(seq) instead of 32 as the 2nd arg to snprintf. [runtime/printf] [3]

[cpplint] reported by reviewdog 🐶 Complex multi-line /*...*/-style comment found. Lint may give bogus warnings. Consider replacing these with //-style comments, with #if 0...#endif, or with more clearly structured multi-line comments. [readability/multiline_comment] [5] Raw Output: src/kilo.c:445: Complex multi-line /*...*/-style comment found. Lint may give bogus warnings. Consider replacing these with //-style comments, with #if 0...#endif, or with more clearly structured multi-line comments. [readability/multiline_comment] [5]

[cpplint] reported by reviewdog 🐶 Use int16/int64/etc, rather than the C type long [runtime/int] [4] Raw Output: src/kilo.c:598: Use int16/int64/etc, rather than the C type long [runtime/int] [4]