oksutils
Unit Tests
No unit tests written.
Clang Formatting
| File | Status |
|---|---|
| apps/oks_diff_data.cxx | ❌ Needs formatting |
| apps/oks_diff_schema.cxx | ❌ Needs formatting |
| apps/oks_get_data.cxx | ❌ Needs formatting |
| apps/oks_get_schema.cxx | ❌ Needs formatting |
| apps/oks_ls_data.cxx | ❌ Needs formatting |
| apps/oks_merge.cxx | ❌ Needs formatting |
| apps/oks_refresh.cxx | ❌ Needs formatting |
| apps/oks_report_equal_objects.cxx | ❌ Needs formatting |
| apps/oks_report_no_descriptions.cxx | ❌ Needs formatting |
| apps/oks_tutorial.cxx | ❌ Needs formatting |
| include/oksutils/oks/access.hpp | ❌ Needs formatting |
| include/oksutils/oks/ral.hpp | ❌ Needs formatting |
| include/oksutils/oks/tz.hpp | ❌ Needs formatting |
| src/lib/oks_access.cpp | ❌ Needs formatting |
| src/lib/oks_tz.cpp | ❌ Needs formatting |
| test/apps/alloc.cxx | ❌ Needs formatting |
| test/apps/and_expression.cxx | ❌ Needs formatting |
| test/apps/attribute.cxx | ❌ Needs formatting |
| test/apps/class.cxx | ❌ Needs formatting |
| test/apps/comparator.cxx | ❌ Needs formatting |
| test/apps/data.cxx | ❌ Needs formatting |
| test/apps/generate_data.cxx | ❌ Needs formatting |
| test/apps/index.cxx | ❌ Needs formatting |
| test/apps/kernel.cxx | ❌ Needs formatting |
| test/apps/method.cxx | ❌ Needs formatting |
| test/apps/not_expression.cxx | ❌ Needs formatting |
| test/apps/object.cxx | ❌ Needs formatting |
| test/apps/or_expression.cxx | ❌ Needs formatting |
| test/apps/profiler.cxx | ❌ Needs formatting |
| test/apps/query.cxx | ❌ Needs formatting |
| test/apps/r_expression.cxx | ❌ Needs formatting |
| test/apps/relationship.cxx | ❌ Needs formatting |
| test/apps/test_indexies.cxx | ❌ Needs formatting |
| test/apps/time_tests.cxx | ❌ Needs formatting |
apps/oks_diff_data.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 46: Found other header after system header. Should be: oks_diff_data.hh, other non-system headers, system headers.
- Line 47: Found other header after system header. Should be: oks_diff_data.hh, other non-system headers, system headers.
- Line 48: Found other header after system header. Should be: oks_diff_data.hh, other non-system headers, system headers.
- Line 49: Found other header after system header. Should be: oks_diff_data.hh, other non-system headers, system headers.
- Line 50: Found other header after system header. Should be: oks_diff_data.hh, other non-system headers, system headers.
- Line 61: "cout" should not be used for output in DUNE DAQ software.
- Line 79: "cout" should not be used for output in DUNE DAQ software.
- Line 84: "cout" should not be used for output in DUNE DAQ software.
- Line 87: If an else has a brace on one side, it should have it on both
- Line 94: If an else has a brace on one side, it should have it on both
- Line 96: "cout" should not be used for output in DUNE DAQ software.
- Line 192: If an else has a brace on one side, it should have it on both
- Line 199: If an else has a brace on one side, it should have it on both
- Line 203: If an else has a brace on one side, it should have it on both
- Line 207: If an else has a brace on one side, it should have it on both
- Line 208: "cout" should not be used for output in DUNE DAQ software.
- Line 211: If an else has a brace on one side, it should have it on both
- Line 213: Else clause should be indented at the same level as if. Ambiguous nested if/else chains require braces.
- Line 214: If an else has a brace on one side, it should have it on both
- Line 221: If an else has a brace on one side, it should have it on both
- Line 222: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 222: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 224: If an else has a brace on one side, it should have it on both
- Line 225: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 225: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 227: If an else has a brace on one side, it should have it on both
- Line 228: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 228: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 230: If an else has a brace on one side, it should have it on both
- Line 231: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 231: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 233: If an else has a brace on one side, it should have it on both
- Line 234: "cerr" should not be used for output in DUNE DAQ software.
- Line 244: "cerr" should not be used for output in DUNE DAQ software.
- Line 250: "cerr" should not be used for output in DUNE DAQ software.
- Line 259: "cerr" should not be used for output in DUNE DAQ software.
- Line 294: "cerr" should not be used for output in DUNE DAQ software.
- Line 298: "cout" should not be used for output in DUNE DAQ software.
- Line 314: "cout" should not be used for output in DUNE DAQ software.
- Line 315: "cout" should not be used for output in DUNE DAQ software.
- Line 319: "cout" should not be used for output in DUNE DAQ software.
- Line 320: "cout" should not be used for output in DUNE DAQ software.
- Line 320: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 326: "cout" should not be used for output in DUNE DAQ software.
- Line 327: "cout" should not be used for output in DUNE DAQ software.
- Line 327: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 347: "cout" should not be used for output in DUNE DAQ software.
- Line 348: "cout" should not be used for output in DUNE DAQ software.
- Line 348: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 355: "cout" should not be used for output in DUNE DAQ software.
- Line 356: "cout" should not be used for output in DUNE DAQ software.
- Line 356: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 374: "cout" should not be used for output in DUNE DAQ software.
- Line 394: "cout" should not be used for output in DUNE DAQ software.
- Line 404: "cout" should not be used for output in DUNE DAQ software.
- Line 405: "cout" should not be used for output in DUNE DAQ software.
- Line 406: "cout" should not be used for output in DUNE DAQ software.
- Line 418: "cout" should not be used for output in DUNE DAQ software.
- Line 419: "cout" should not be used for output in DUNE DAQ software.
- Line 419: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 425: "cout" should not be used for output in DUNE DAQ software.
- Line 431: "cerr" should not be used for output in DUNE DAQ software.
- Line 436: "cerr" should not be used for output in DUNE DAQ software.
- Line 441: "cerr" should not be used for output in DUNE DAQ software.
- Line 445: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 448: "cout" should not be used for output in DUNE DAQ software.
- Line 451: Small and focused functions are preferred: main() has 225 non-comment lines (error triggered by exceeding 80 lines) (disable this by putting "// NOLINT" after the function's closing brace.)
- Line 414: Add #include
for string - Line 67: Add #include
for less<> - Line 385: Add #include
- for list<>
Warnings
- Line 74: use auto when declaring iterators
- Line 177: do not use pointer arithmetic
- Line 177: use nullptr
- Line 179: use nullptr
- Line 180: use nullptr
- Line 182: use nullptr
- Line 183: use nullptr
- Line 186: do not use pointer arithmetic
- Line 186: do not use pointer arithmetic
- Line 188: do not use pointer arithmetic
- Line 188: do not use pointer arithmetic
- Line 190: do not use pointer arithmetic
- Line 190: do not use pointer arithmetic
- Line 192: do not use pointer arithmetic
- Line 192: do not use pointer arithmetic
- Line 197: do not use pointer arithmetic
- Line 197: do not use pointer arithmetic
- Line 199: do not use pointer arithmetic
- Line 203: do not use pointer arithmetic
- Line 207: do not use pointer arithmetic
- Line 207: do not use pointer arithmetic
- Line 211: do not use pointer arithmetic
- Line 211: do not use pointer arithmetic
- Line 213: do not use pointer arithmetic
- Line 213: do not use pointer arithmetic
- Line 213: do not use pointer arithmetic
- Line 215: do not use pointer arithmetic
- Line 215: use nullptr
- Line 221: do not use pointer arithmetic
- Line 221: do not use pointer arithmetic
- Line 222: do not use pointer arithmetic
- Line 222: do not use pointer arithmetic
- Line 224: do not use pointer arithmetic
- Line 224: do not use pointer arithmetic
- Line 225: do not use pointer arithmetic
- Line 225: do not use pointer arithmetic
- Line 227: do not use pointer arithmetic
- Line 227: do not use pointer arithmetic
- Line 228: do not use pointer arithmetic
- Line 228: do not use pointer arithmetic
- Line 230: do not use pointer arithmetic
- Line 230: do not use pointer arithmetic
- Line 231: do not use pointer arithmetic
- Line 231: do not use pointer arithmetic
- Line 234: do not use pointer arithmetic
- Line 243: use nullptr
- Line 244: Potential leak of memory pointed to by 'schemaFiles'
- Line 249: use nullptr
- Line 280: do not use pointer arithmetic
- Line 280: use nullptr
- Line 281: do not use pointer arithmetic
- Line 291: use auto when declaring iterators
- Line 302: multiple declarations in a single statement reduces readability
- Line 302: variable 'c1' is not initialized
- Line 302: variable 'c2' is not initialized
- Line 334: use auto when declaring iterators
- Line 365: use auto when declaring iterators
- Line 385: use auto when declaring iterators
apps/oks_diff_schema.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 546: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 576: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 38: Found other header after system header. Should be: oks_diff_schema.hh, other non-system headers, system headers.
- Line 39: Found other header after system header. Should be: oks_diff_schema.hh, other non-system headers, system headers.
- Line 40: Found other header after system header. Should be: oks_diff_schema.hh, other non-system headers, system headers.
- Line 41: Found other header after system header. Should be: oks_diff_schema.hh, other non-system headers, system headers.
- Line 42: Found other header after system header. Should be: oks_diff_schema.hh, other non-system headers, system headers.
- Line 60: "cout" should not be used for output in DUNE DAQ software.
- Line 63: "cout" should not be used for output in DUNE DAQ software.
- Line 109: "cout" should not be used for output in DUNE DAQ software.
- Line 109: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 116: "cout" should not be used for output in DUNE DAQ software.
- Line 116: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 120: "cout" should not be used for output in DUNE DAQ software.
- Line 121: If an else has a brace on one side, it should have it on both
- Line 131: "cout" should not be used for output in DUNE DAQ software.
- Line 134: "cout" should not be used for output in DUNE DAQ software.
- Line 134: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 140: "cout" should not be used for output in DUNE DAQ software.
- Line 140: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 146: "cout" should not be used for output in DUNE DAQ software.
- Line 146: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 152: "cout" should not be used for output in DUNE DAQ software.
- Line 152: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 158: "cout" should not be used for output in DUNE DAQ software.
- Line 158: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 164: "cout" should not be used for output in DUNE DAQ software.
- Line 164: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 180: "cout" should not be used for output in DUNE DAQ software.
- Line 180: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 203: "cout" should not be used for output in DUNE DAQ software.
- Line 203: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 210: "cout" should not be used for output in DUNE DAQ software.
- Line 210: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 213: "cout" should not be used for output in DUNE DAQ software.
- Line 214: If an else has a brace on one side, it should have it on both
- Line 230: "cout" should not be used for output in DUNE DAQ software.
- Line 233: "cout" should not be used for output in DUNE DAQ software.
- Line 233: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 239: "cout" should not be used for output in DUNE DAQ software.
- Line 239: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 245: "cout" should not be used for output in DUNE DAQ software.
- Line 245: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 251: "cout" should not be used for output in DUNE DAQ software.
- Line 251: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 257: "cout" should not be used for output in DUNE DAQ software.
- Line 257: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 263: "cout" should not be used for output in DUNE DAQ software.
- Line 263: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 268: If/else bodies with multiple statements require braces
- Line 269: "cout" should not be used for output in DUNE DAQ software.
- Line 269: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 287: "cout" should not be used for output in DUNE DAQ software.
- Line 287: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 294: Small and focused functions are preferred: relationshipsTest() has 83 non-comment lines (error triggered by exceeding 80 lines) (disable this by putting "// NOLINT" after the function's closing brace.)
- Line 309: "cout" should not be used for output in DUNE DAQ software.
- Line 309: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 316: "cout" should not be used for output in DUNE DAQ software.
- Line 316: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 320: "cout" should not be used for output in DUNE DAQ software.
- Line 321: If an else has a brace on one side, it should have it on both
- Line 325: "cout" should not be used for output in DUNE DAQ software.
- Line 328: "cout" should not be used for output in DUNE DAQ software.
- Line 328: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 339: "cout" should not be used for output in DUNE DAQ software.
- Line 339: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 344: If an else has a brace on one side, it should have it on both
- Line 345: "cout" should not be used for output in DUNE DAQ software.
- Line 345: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 350: If an else has a brace on one side, it should have it on both
- Line 351: "cout" should not be used for output in DUNE DAQ software.
- Line 351: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 356: If an else has a brace on one side, it should have it on both
- Line 366: "cout" should not be used for output in DUNE DAQ software.
- Line 366: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 374: "cout" should not be used for output in DUNE DAQ software.
- Line 374: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 382: "cout" should not be used for output in DUNE DAQ software.
- Line 382: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 404: "cout" should not be used for output in DUNE DAQ software.
- Line 404: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 411: Small and focused functions are preferred: methodsTest() has 92 non-comment lines (error triggered by exceeding 80 lines) (disable this by putting "// NOLINT" after the function's closing brace.)
- Line 435: If an else has a brace on one side, it should have it on both
- Line 441: If an else has a brace on one side, it should have it on both
- Line 445: If an else has a brace on one side, it should have it on both
- Line 446: "cout" should not be used for output in DUNE DAQ software.
- Line 449: If an else has a brace on one side, it should have it on both
- Line 450: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 451: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 453: If an else has a brace on one side, it should have it on both
- Line 454: "cerr" should not be used for output in DUNE DAQ software.
- Line 477: "cerr" should not be used for output in DUNE DAQ software.
- Line 482: "cerr" should not be used for output in DUNE DAQ software.
- Line 489: "cout" should not be used for output in DUNE DAQ software.
- Line 501: "cout" should not be used for output in DUNE DAQ software.
- Line 501: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 506: "cout" should not be used for output in DUNE DAQ software.
- Line 507: "cout" should not be used for output in DUNE DAQ software.
- Line 518: "cout" should not be used for output in DUNE DAQ software.
- Line 522: "cout" should not be used for output in DUNE DAQ software.
- Line 522: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 532: "cout" should not be used for output in DUNE DAQ software.
- Line 532: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 539: "cout" should not be used for output in DUNE DAQ software.
- Line 539: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 555: "cout" should not be used for output in DUNE DAQ software.
- Line 555: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 569: "cout" should not be used for output in DUNE DAQ software.
- Line 569: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 580: "cout" should not be used for output in DUNE DAQ software.
- Line 581: "cout" should not be used for output in DUNE DAQ software.
- Line 582: "cout" should not be used for output in DUNE DAQ software.
- Line 588: "cout" should not be used for output in DUNE DAQ software.
- Line 588: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 592: "cout" should not be used for output in DUNE DAQ software.
- Line 596: "cerr" should not be used for output in DUNE DAQ software.
- Line 601: "cerr" should not be used for output in DUNE DAQ software.
- Line 606: Small and focused functions are preferred: main() has 142 non-comment lines (error triggered by exceeding 80 lines) (disable this by putting "// NOLINT" after the function's closing brace.)
- Line 566: Add #include
- for list<>
- Line 566: Add #include
for string
Warnings
- Line 49: use nullptr
- Line 50: use nullptr
- Line 59: use auto when declaring iterators
- Line 67: declaration uses identifier '__Success__', which is a reserved identifier
- Line 68: declaration uses identifier '__StartOfBadStatus__', which is a reserved identifier
- Line 69: declaration uses identifier '__BadCommandLine__', which is a reserved identifier
- Line 70: declaration uses identifier '__CannotReadFile__', which is a reserved identifier
- Line 71: declaration uses identifier '__ThereAreNoClasses__', which is a reserved identifier
- Line 101: multiple declarations in a single statement reduces readability
- Line 101: variable 'a1' is not initialized
- Line 101: variable 'a2' is not initialized
- Line 104: use auto when declaring iterators
- Line 176: use auto when declaring iterators
- Line 179: Although the value stored to 'a1' is used in the enclosing expression, the value is never actually read from 'a1'
- Line 195: multiple declarations in a single statement reduces readability
- Line 195: variable 'r1' is not initialized
- Line 195: variable 'r2' is not initialized
- Line 198: use auto when declaring iterators
- Line 282: use auto when declaring iterators
- Line 286: Although the value stored to 'r1' is used in the enclosing expression, the value is never actually read from 'r1'
- Line 301: multiple declarations in a single statement reduces readability
- Line 301: variable 'm1' is not initialized
- Line 301: variable 'm2' is not initialized
- Line 304: use auto when declaring iterators
- Line 338: use nullptr
- Line 344: use nullptr
- Line 357: use auto when declaring iterators
- Line 358: use auto when declaring iterators
- Line 400: use auto when declaring iterators
- Line 403: Although the value stored to 'm1' is used in the enclosing expression, the value is never actually read from 'm1'
- Line 427: do not use pointer arithmetic
- Line 429: do not use pointer arithmetic
- Line 431: do not use pointer arithmetic
- Line 433: do not use pointer arithmetic
- Line 435: do not use pointer arithmetic
- Line 441: do not use pointer arithmetic
- Line 441: do not use pointer arithmetic
- Line 445: do not use pointer arithmetic
- Line 449: do not use pointer arithmetic
- Line 449: do not use pointer arithmetic
- Line 450: do not use pointer arithmetic
- Line 451: do not use pointer arithmetic
- Line 454: do not use pointer arithmetic
- Line 486: use auto when declaring iterators
- Line 487: use auto when declaring iterators
- Line 494: multiple declarations in a single statement reduces readability
- Line 494: variable 'c1' is not initialized
- Line 494: variable 'c2' is not initialized
- Line 549: variable 'spn' is not initialized
- Line 552: use auto when declaring iterators
- Line 566: use auto when declaring iterators
apps/oks_get_data.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 12: Found other header after system header. Should be: oks_get_data.hh, other non-system headers, system headers.
- Line 13: Found other header after system header. Should be: oks_get_data.hh, other non-system headers, system headers.
- Line 14: Found other header after system header. Should be: oks_get_data.hh, other non-system headers, system headers.
- Line 15: Found other header after system header. Should be: oks_get_data.hh, other non-system headers, system headers.
- Line 16: Found other header after system header. Should be: oks_get_data.hh, other non-system headers, system headers.
- Line 18: Found other header after system header. Should be: oks_get_data.hh, other non-system headers, system headers.
- Line 19: Found other header after system header. Should be: oks_get_data.hh, other non-system headers, system headers.
- Line 24: "cout" should not be used for output in DUNE DAQ software.
- Line 60: "cerr" should not be used for output in DUNE DAQ software.
- Line 78: Use int16/int64/etc, rather than the C type long
- Line 91: If an else has a brace on one side, it should have it on both
- Line 92: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 94: If an else has a brace on one side, it should have it on both
- Line 96: "cerr" should not be used for output in DUNE DAQ software.
- Line 101: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 103: If an else has a brace on one side, it should have it on both
- Line 104: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 106: If an else has a brace on one side, it should have it on both
- Line 107: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 109: If an else has a brace on one side, it should have it on both
- Line 110: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 112: "cerr" should not be used for output in DUNE DAQ software.
- Line 119: If an else has a brace on one side, it should have it on both
- Line 120: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 122: If an else has a brace on one side, it should have it on both
- Line 123: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 125: If an else has a brace on one side, it should have it on both
- Line 126: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 128: If an else has a brace on one side, it should have it on both
- Line 129: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 131: If an else has a brace on one side, it should have it on both
- Line 132: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 132: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 134: If an else has a brace on one side, it should have it on both
- Line 135: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 137: If an else has a brace on one side, it should have it on both
- Line 138: "cerr" should not be used for output in DUNE DAQ software.
- Line 145: "cerr" should not be used for output in DUNE DAQ software.
- Line 149: If an else has a brace on one side, it should have it on both
- Line 150: "cerr" should not be used for output in DUNE DAQ software.
- Line 154: If an else has a brace on one side, it should have it on both
- Line 155: "cerr" should not be used for output in DUNE DAQ software.
- Line 161: "cerr" should not be used for output in DUNE DAQ software.
- Line 167: "cerr" should not be used for output in DUNE DAQ software.
- Line 242: Use int16/int64/etc, rather than the C type long
- Line 246: If an else has a brace on one side, it should have it on both
- Line 247: "cerr" should not be used for output in DUNE DAQ software.
- Line 253: If an else has a brace on one side, it should have it on both
- Line 254: "cerr" should not be used for output in DUNE DAQ software.
- Line 260: If an else has a brace on one side, it should have it on both
- Line 261: "cerr" should not be used for output in DUNE DAQ software.
- Line 268: "cout" should not be used for output in DUNE DAQ software.
- Line 271: "cout" should not be used for output in DUNE DAQ software.
- Line 279: "cerr" should not be used for output in DUNE DAQ software.
- Line 302: If an else has a brace on one side, it should have it on both
- Line 312: If an else has a brace on one side, it should have it on both
- Line 321: "cerr" should not be used for output in DUNE DAQ software.
- Line 326: "cerr" should not be used for output in DUNE DAQ software.
- Line 331: "cerr" should not be used for output in DUNE DAQ software.
- Line 336: "cerr" should not be used for output in DUNE DAQ software.
- Line 341: Small and focused functions are preferred: main() has 226 non-comment lines (error triggered by exceeding 80 lines) (disable this by putting "// NOLINT" after the function's closing brace.)
- Line 275: Add #include
for string - Line 207: Add #include
for unique_ptr<>
Warnings
- Line 22: modification of 'std' namespace can result in undefined behavior
- Line 58: modification of 'std' namespace can result in undefined behavior
- Line 64: modification of 'std' namespace can result in undefined behavior
- Line 64: do not declare C-style arrays, use std::array<> instead
- Line 78: consider replacing 'long' with 'int64'
- Line 85: do not use pointer arithmetic
- Line 92: 'atoi' used to convert a string to an integer value, but function will not report conversion errors; consider using 'strtol' instead
- Line 92: do not use pointer arithmetic
- Line 101: do not use pointer arithmetic
- Line 101: do not use pointer arithmetic
- Line 104: do not use pointer arithmetic
- Line 107: 'atoi' used to convert a string to an integer value, but function will not report conversion errors; consider using 'strtol' instead
- Line 107: do not use pointer arithmetic
- Line 116: 'atoi' used to convert a string to an integer value, but function will not report conversion errors; consider using 'strtol' instead
- Line 116: do not use pointer arithmetic
- Line 120: do not use pointer arithmetic
- Line 123: do not use pointer arithmetic
- Line 126: do not use pointer arithmetic
- Line 129: do not use pointer arithmetic
- Line 132: do not use pointer arithmetic
- Line 132: do not use pointer arithmetic
- Line 135: 'atoi' used to convert a string to an integer value, but function will not report conversion errors; consider using 'strtol' instead
- Line 135: do not use pointer arithmetic
- Line 242: consider replacing 'unsigned long' with 'uint64'
apps/oks_get_schema.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 18: Found other header after system header. Should be: oks_get_schema.hh, other non-system headers, system headers.
- Line 19: Found other header after system header. Should be: oks_get_schema.hh, other non-system headers, system headers.
- Line 24: "cout" should not be used for output in DUNE DAQ software.
- Line 51: "cerr" should not be used for output in DUNE DAQ software.
- Line 76: If an else has a brace on one side, it should have it on both
- Line 77: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 79: If an else has a brace on one side, it should have it on both
- Line 80: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 82: If an else has a brace on one side, it should have it on both
- Line 84: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 86: If an else has a brace on one side, it should have it on both
- Line 87: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 89: If an else has a brace on one side, it should have it on both
- Line 90: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 92: If an else has a brace on one side, it should have it on both
- Line 93: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 95: If an else has a brace on one side, it should have it on both
- Line 96: "cerr" should not be used for output in DUNE DAQ software.
- Line 103: "cerr" should not be used for output in DUNE DAQ software.
- Line 109: "cerr" should not be used for output in DUNE DAQ software.
- Line 115: "cerr" should not be used for output in DUNE DAQ software.
- Line 170: If an else has a brace on one side, it should have it on both
- Line 180: "cerr" should not be used for output in DUNE DAQ software.
- Line 185: "cerr" should not be used for output in DUNE DAQ software.
- Line 190: "cerr" should not be used for output in DUNE DAQ software.
- Line 195: "cerr" should not be used for output in DUNE DAQ software.
- Line 200: Small and focused functions are preferred: main() has 110 non-comment lines (error triggered by exceeding 80 lines) (disable this by putting "// NOLINT" after the function's closing brace.)
- Line 65: Add #include
for string - Line 144: Add #include
for unique_ptr<>
Warnings
- Line 22: modification of 'std' namespace can result in undefined behavior
- Line 49: modification of 'std' namespace can result in undefined behavior
- Line 55: modification of 'std' namespace can result in undefined behavior
- Line 55: do not declare C-style arrays, use std::array<> instead
- Line 70: do not use pointer arithmetic
- Line 77: 'atoi' used to convert a string to an integer value, but function will not report conversion errors; consider using 'strtol' instead
- Line 77: do not use pointer arithmetic
- Line 80: 'atoi' used to convert a string to an integer value, but function will not report conversion errors; consider using 'strtol' instead
- Line 80: do not use pointer arithmetic
- Line 84: do not use pointer arithmetic
- Line 84: do not use pointer arithmetic
- Line 87: do not use pointer arithmetic
- Line 90: do not use pointer arithmetic
- Line 93: do not use pointer arithmetic
apps/oks_ls_data.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 370: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 10: Found other header after system header. Should be: oks_ls_data.hh, other non-system headers, system headers.
- Line 11: Found other header after system header. Should be: oks_ls_data.hh, other non-system headers, system headers.
- Line 16: Found other header after system header. Should be: oks_ls_data.hh, other non-system headers, system headers.
- Line 17: Found other header after system header. Should be: oks_ls_data.hh, other non-system headers, system headers.
- Line 18: Found other header after system header. Should be: oks_ls_data.hh, other non-system headers, system headers.
- Line 21: "RelationalAccess/ITransaction.h" already included at sourcecode/oksutils/apps/oks_ls_data.cxx:16
- Line 31: Found other header after system header. Should be: oks_ls_data.hh, other non-system headers, system headers.
- Line 33: Found other header after system header. Should be: oks_ls_data.hh, other non-system headers, system headers.
- Line 34: Found other header after system header. Should be: oks_ls_data.hh, other non-system headers, system headers.
- Line 48: Use int16/int64/etc, rather than the C type long
- Line 83: "cout" should not be used for output in DUNE DAQ software.
- Line 154: "cerr" should not be used for output in DUNE DAQ software.
- Line 197: If an else has a brace on one side, it should have it on both
- Line 198: If an else has a brace on one side, it should have it on both
- Line 199: If an else has a brace on one side, it should have it on both
- Line 200: If an else has a brace on one side, it should have it on both
- Line 201: If an else has a brace on one side, it should have it on both
- Line 203: If an else has a brace on one side, it should have it on both
- Line 204: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 206: If an else has a brace on one side, it should have it on both
- Line 207: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 209: If an else has a brace on one side, it should have it on both
- Line 210: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 212: If an else has a brace on one side, it should have it on both
- Line 213: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 215: If an else has a brace on one side, it should have it on both
- Line 216: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 218: If an else has a brace on one side, it should have it on both
- Line 219: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 221: If an else has a brace on one side, it should have it on both
- Line 222: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 224: If an else has a brace on one side, it should have it on both
- Line 225: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 227: If an else has a brace on one side, it should have it on both
- Line 228: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 230: If an else has a brace on one side, it should have it on both
- Line 231: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 233: If an else has a brace on one side, it should have it on both
- Line 234: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 236: If an else has a brace on one side, it should have it on both
- Line 237: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 239: If an else has a brace on one side, it should have it on both
- Line 240: "cerr" should not be used for output in DUNE DAQ software.
- Line 256: "cout" should not be used for output in DUNE DAQ software.
- Line 265: "cerr" should not be used for output in DUNE DAQ software.
- Line 271: "cerr" should not be used for output in DUNE DAQ software.
- Line 277: "cerr" should not be used for output in DUNE DAQ software.
- Line 300: "cerr" should not be used for output in DUNE DAQ software.
- Line 325: "cout" should not be used for output in DUNE DAQ software.
- Line 328: "cout" should not be used for output in DUNE DAQ software.
- Line 331: If an else has a brace on one side, it should have it on both
- Line 406: If an else has a brace on one side, it should have it on both
- Line 410: If an else has a brace on one side, it should have it on both
- Line 447: If an else has a brace on one side, it should have it on both
- Line 519: Use int16/int64/etc, rather than the C type long
- Line 532: If/else bodies with multiple statements require braces
- Line 533: If/else bodies with multiple statements require braces
- Line 555: Using C-style cast. Use static_cast
(...) instead - Line 555: Use int16/int64/etc, rather than the C type long
- Line 628: If/else bodies with multiple statements require braces
- Line 642: Use int16/int64/etc, rather than the C type short
- Line 645: Use int16/int64/etc, rather than the C type short
- Line 646: Use int16/int64/etc, rather than the C type short
- Line 659: "cout" should not be used for output in DUNE DAQ software.
- Line 660: Use int16/int64/etc, rather than the C type short
- Line 661: "cout" should not be used for output in DUNE DAQ software.
- Line 662: "cout" should not be used for output in DUNE DAQ software.
- Line 663: "cout" should not be used for output in DUNE DAQ software.
- Line 664: "cout" should not be used for output in DUNE DAQ software.
- Line 666: "cout" should not be used for output in DUNE DAQ software.
- Line 681: "cerr" should not be used for output in DUNE DAQ software.
- Line 686: "cerr" should not be used for output in DUNE DAQ software.
- Line 691: "cerr" should not be used for output in DUNE DAQ software.
- Line 698: Small and focused functions are preferred: main() has 411 non-comment lines (error triggered by exceeding 80 lines) (disable this by putting "// NOLINT" after the function's closing brace.)
- Line 628: Add #include
for string - Line 569: Add #include
for unique_ptr<> - Line 327: Add #include
for set<> - Line 658: Add #include
for vector<>
Warnings
- Line 27: inclusion of deprecated C++ header 'stdlib.h'; consider using 'cstdlib' instead
- Line 41: modification of 'std' namespace can result in undefined behavior
- Line 44: do not declare C-style arrays, use std::array<> instead
- Line 48: consider replacing 'long' with 'int64'
- Line 48: consider replacing 'long' with 'int64'
- Line 48: consider replacing 'long' with 'int64'
- Line 81: modification of 'std' namespace can result in undefined behavior
- Line 152: modification of 'std' namespace can result in undefined behavior
- Line 158: modification of 'std' namespace can result in undefined behavior
- Line 167: modification of 'std' namespace can result in undefined behavior
- Line 167: do not declare C-style arrays, use std::array<> instead
- Line 188: use nullptr
- Line 189: use nullptr
- Line 190: use nullptr
- Line 194: do not use pointer arithmetic
- Line 204: do not use pointer arithmetic
- Line 207: do not use pointer arithmetic
- Line 210: do not use pointer arithmetic
- Line 213: do not use pointer arithmetic
- Line 216: do not use pointer arithmetic
- Line 219: 'atoi' used to convert a string to an integer value, but function will not report conversion errors; consider using 'strtol' instead
- Line 219: do not use pointer arithmetic
- Line 222: 'atoi' used to convert a string to an integer value, but function will not report conversion errors; consider using 'strtol' instead
- Line 222: do not use pointer arithmetic
- Line 225: do not use pointer arithmetic
- Line 228: do not use pointer arithmetic
- Line 231: do not use pointer arithmetic
- Line 234: do not use pointer arithmetic
- Line 237: do not use pointer arithmetic
- Line 471: do not use pointer arithmetic
- Line 518: do not declare C-style arrays, use std::array<> instead
- Line 519: consider replacing 'long' with 'int64'
- Line 555: C-style casts are discouraged; use static_cast/const_cast/reinterpret_cast
- Line 555: consider replacing 'long' with 'int64'
- Line 583: do not use pointer arithmetic
- Line 642: consider replacing 'unsigned short' with 'uint16'
- Line 642: do not declare C-style arrays, use std::array<> instead
- Line 656: do not declare C-style arrays, use std::array<> instead
- Line 660: consider replacing 'unsigned short' with 'uint16'
- Line 660: loop variable has narrower type 'unsigned short' than iteration's upper bound 'unsigned long'
- Line 660: consider replacing 'unsigned short' with 'uint16'
apps/oks_merge.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 120: Use int16/int64/etc, rather than the C type long
- Line 141: If an else has a brace on one side, it should have it on both
- Line 142: "cout" should not be used for output in DUNE DAQ software.
- Line 145: If an else has a brace on one side, it should have it on both
- Line 146: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 148: If an else has a brace on one side, it should have it on both
- Line 149: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 151: If an else has a brace on one side, it should have it on both
- Line 152: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 154: If an else has a brace on one side, it should have it on both
- Line 155: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 157: If an else has a brace on one side, it should have it on both
- Line 158: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 165: If an else has a brace on one side, it should have it on both
- Line 224: "cout" should not be used for output in DUNE DAQ software.
- Line 227: "cout" should not be used for output in DUNE DAQ software.
- Line 235: "cout" should not be used for output in DUNE DAQ software.
- Line 237: If an else has a brace on one side, it should have it on both
- Line 241: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 246: If an else has a brace on one side, it should have it on both
- Line 247: "cout" should not be used for output in DUNE DAQ software.
- Line 250: If an else has a brace on one side, it should have it on both
- Line 254: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 256: If an else has a brace on one side, it should have it on both
- Line 257: "cout" should not be used for output in DUNE DAQ software.
- Line 260: If an else has a brace on one side, it should have it on both
- Line 265: If an else has a brace on one side, it should have it on both
- Line 292: Small and focused functions are preferred: main() has 156 non-comment lines (error triggered by exceeding 80 lines) (disable this by putting "// NOLINT" after the function's closing brace.)
- Line 121: Add #include
for string - Line 121: Add #include
for vector<>
Warnings
- Line 88: declaration uses identifier '__OksMergeExitStatus__', which is a reserved identifier
- Line 89: declaration uses identifier '__Success__', which is a reserved identifier
- Line 90: declaration uses identifier '__NoDataFilesLoaded__', which is a reserved identifier
- Line 91: declaration uses identifier '__NoSchemaFilesLoaded__', which is a reserved identifier
- Line 92: declaration uses identifier '__BadCommandLine__', which is a reserved identifier
- Line 93: declaration uses identifier '__NoOutputSchemaFile__', which is a reserved identifier
- Line 94: declaration uses identifier '__BadQuery__', which is a reserved identifier
- Line 95: declaration uses identifier '__NoSuchClass__', which is a reserved identifier
- Line 96: declaration uses identifier '__ExceptionCaught__', which is a reserved identifier
- Line 120: consider replacing 'long' with 'int64'
- Line 135: do not use pointer arithmetic
- Line 146: do not use pointer arithmetic
- Line 149: do not use pointer arithmetic
- Line 152: do not use pointer arithmetic
- Line 155: do not use pointer arithmetic
- Line 158: 'atol' used to convert a string to an integer value, but function will not report conversion errors; consider using 'strtol' instead
- Line 158: do not use pointer arithmetic
- Line 161: do not use pointer arithmetic
- Line 161: use emplace_back instead of push_back
- Line 161: do not use pointer arithmetic
- Line 186: use nullptr
- Line 187: use nullptr
- Line 205: use auto when declaring iterators
- Line 220: use auto when initializing with new to avoid duplicating the type name
- Line 242: use auto when declaring iterators
- Line 266: use auto when declaring iterators
apps/oks_refresh.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 19: Found other header after system header. Should be: oks_refresh.hh, other non-system headers, system headers.
- Line 48: "cout" should not be used for output in DUNE DAQ software.
- Line 57: "cerr" should not be used for output in DUNE DAQ software.
- Line 64: "cout" should not be used for output in DUNE DAQ software.
- Line 37: Add #include
for string - Line 37: Add #include
for vector<>
Warnings
- Line 15: inclusion of deprecated C++ header 'stdlib.h'; consider using 'cstdlib' instead
apps/oks_report_equal_objects.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 26: Found other header after system header. Should be: oks_report_equal_objects.hh, other non-system headers, system headers.
- Line 27: Found other header after system header. Should be: oks_report_equal_objects.hh, other non-system headers, system headers.
- Line 28: Found other header after system header. Should be: oks_report_equal_objects.hh, other non-system headers, system headers.
- Line 29: Found other header after system header. Should be: oks_report_equal_objects.hh, other non-system headers, system headers.
- Line 30: Found other header after system header. Should be: oks_report_equal_objects.hh, other non-system headers, system headers.
- Line 52: "cout" should not be used for output in DUNE DAQ software.
- Line 59: "cout" should not be used for output in DUNE DAQ software.
- Line 106: If an else has a brace on one side, it should have it on both
- Line 108: "cout" should not be used for output in DUNE DAQ software.
- Line 112: "cout" should not be used for output in DUNE DAQ software.
- Line 114: "cout" should not be used for output in DUNE DAQ software.
- Line 124: If an else has a brace on one side, it should have it on both
- Line 160: "cout" should not be used for output in DUNE DAQ software.
- Line 166: "cerr" should not be used for output in DUNE DAQ software.
- Line 184: If an else has a brace on one side, it should have it on both
- Line 185: "cerr" should not be used for output in DUNE DAQ software.
- Line 195: "cerr" should not be used for output in DUNE DAQ software.
- Line 175: Add #include
for string - Line 83: Add #include
- for list<>
- Line 90: Add #include
for make_pair - Line 175: Add #include
for vector<>
Warnings
- Line 69: C-style casts are discouraged; use static_cast/const_cast/reinterpret_cast
- Line 69: use nullptr
- Line 71: use auto when declaring iterators
- Line 77: use auto when declaring iterators
- Line 77: do not use pointer arithmetic
- Line 83: use auto when declaring iterators
- Line 83: do not use pointer arithmetic
- Line 94: use nullptr
- Line 96: use auto when declaring iterators
- Line 113: use auto when declaring iterators
- Line 175: use auto when declaring iterators
- Line 190: use auto when declaring iterators
apps/oks_report_no_descriptions.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 19: Found other header after system header. Should be: oks_report_no_descriptions.hh, other non-system headers, system headers.
- Line 20: Found other header after system header. Should be: oks_report_no_descriptions.hh, other non-system headers, system headers.
- Line 21: Found other header after system header. Should be: oks_report_no_descriptions.hh, other non-system headers, system headers.
- Line 22: Found other header after system header. Should be: oks_report_no_descriptions.hh, other non-system headers, system headers.
- Line 23: Found other header after system header. Should be: oks_report_no_descriptions.hh, other non-system headers, system headers.
- Line 24: Found other header after system header. Should be: oks_report_no_descriptions.hh, other non-system headers, system headers.
- Line 45: "cout" should not be used for output in DUNE DAQ software.
- Line 48: "cout" should not be used for output in DUNE DAQ software.
- Line 50: "cout" should not be used for output in DUNE DAQ software.
- Line 88: "cerr" should not be used for output in DUNE DAQ software.
- Line 93: "cerr" should not be used for output in DUNE DAQ software.
- Line 98: "cerr" should not be used for output in DUNE DAQ software.
- Line 102: "cout" should not be used for output in DUNE DAQ software.
- Line 104: "cout" should not be used for output in DUNE DAQ software.
- Line 116: If/else bodies with multiple statements require braces
- Line 126: "cout" should not be used for output in DUNE DAQ software.
- Line 129: If/else bodies with multiple statements require braces
- Line 138: "cout" should not be used for output in DUNE DAQ software.
- Line 129: Add #include
- for list<>
Warnings
- Line 17: inclusion of deprecated C++ header 'stdlib.h'; consider using 'cstdlib' instead
- Line 63: do not use pointer arithmetic
- Line 72: use nullptr
apps/oks_tutorial.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 30: Found other header after system header. Should be: oks_tutorial.hh, other non-system headers, system headers.
- Line 31: Found other header after system header. Should be: oks_tutorial.hh, other non-system headers, system headers.
- Line 32: Found other header after system header. Should be: oks_tutorial.hh, other non-system headers, system headers.
- Line 33: Found other header after system header. Should be: oks_tutorial.hh, other non-system headers, system headers.
- Line 34: Found other header after system header. Should be: oks_tutorial.hh, other non-system headers, system headers.
- Line 35: Found other header after system header. Should be: oks_tutorial.hh, other non-system headers, system headers.
- Line 36: Found other header after system header. Should be: oks_tutorial.hh, other non-system headers, system headers.
- Line 80: "cout" should not be used for output in DUNE DAQ software.
- Line 97: An unsigned integer appears to be used here.
- Line 127: "cout" should not be used for output in DUNE DAQ software.
- Line 160: "cout" should not be used for output in DUNE DAQ software.
- Line 181: "cout" should not be used for output in DUNE DAQ software.
- Line 193: "cout" should not be used for output in DUNE DAQ software.
- Line 197: "cout" should not be used for output in DUNE DAQ software.
- Line 205: "cout" should not be used for output in DUNE DAQ software.
- Line 209: "cout" should not be used for output in DUNE DAQ software.
- Line 333: "cout" should not be used for output in DUNE DAQ software.
- Line 340: "cout" should not be used for output in DUNE DAQ software.
- Line 391: "cout" should not be used for output in DUNE DAQ software.
- Line 405: "cout" should not be used for output in DUNE DAQ software.
- Line 410: "cout" should not be used for output in DUNE DAQ software.
- Line 418: "cout" should not be used for output in DUNE DAQ software.
- Line 424: "cout" should not be used for output in DUNE DAQ software.
- Line 434: "cout" should not be used for output in DUNE DAQ software.
- Line 442: "cout" should not be used for output in DUNE DAQ software.
- Line 449: "cout" should not be used for output in DUNE DAQ software.
- Line 455: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 458: "cout" should not be used for output in DUNE DAQ software.
- Line 462: "cout" should not be used for output in DUNE DAQ software.
- Line 481: "cout" should not be used for output in DUNE DAQ software.
- Line 490: "cout" should not be used for output in DUNE DAQ software.
- Line 497: "cout" should not be used for output in DUNE DAQ software.
- Line 503: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 506: "cout" should not be used for output in DUNE DAQ software.
- Line 512: "cout" should not be used for output in DUNE DAQ software.
- Line 531: "cout" should not be used for output in DUNE DAQ software.
- Line 540: "cout" should not be used for output in DUNE DAQ software.
- Line 547: "cout" should not be used for output in DUNE DAQ software.
- Line 553: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 556: "cout" should not be used for output in DUNE DAQ software.
- Line 559: "cout" should not be used for output in DUNE DAQ software.
- Line 567: "cerr" should not be used for output in DUNE DAQ software.
- Line 573: Small and focused functions are preferred: main() has 236 non-comment lines (error triggered by exceeding 80 lines) (disable this by putting "// NOLINT" after the function's closing brace.)
Warnings
- Line 124: multiple declarations in a single statement reduces readability
- Line 157: multiple declarations in a single statement reduces readability
- Line 175: do not use pointer arithmetic
- Line 176: do not use pointer arithmetic
- Line 177: do not use pointer arithmetic
- Line 178: do not use pointer arithmetic
- Line 181: do not use pointer arithmetic
- Line 186: do not use pointer arithmetic
- Line 187: do not use pointer arithmetic
- Line 218: use auto when initializing with new to avoid duplicating the type name
- Line 237: use auto when initializing with new to avoid duplicating the type name
- Line 264: use auto when initializing with new to avoid duplicating the type name
- Line 271: use auto when initializing with new to avoid duplicating the type name
- Line 281: use auto when initializing with new to avoid duplicating the type name
- Line 299: use auto when initializing with new to avoid duplicating the type name
- Line 306: use auto when initializing with new to avoid duplicating the type name
- Line 316: use auto when initializing with new to avoid duplicating the type name
- Line 349: use auto when initializing with new to avoid duplicating the type name
- Line 350: use auto when initializing with new to avoid duplicating the type name
- Line 351: use auto when initializing with new to avoid duplicating the type name
- Line 352: use auto when initializing with new to avoid duplicating the type name
- Line 353: use auto when initializing with new to avoid duplicating the type name
- Line 354: use auto when initializing with new to avoid duplicating the type name
- Line 355: use auto when initializing with new to avoid duplicating the type name
- Line 356: use auto when initializing with new to avoid duplicating the type name
- Line 446: use auto when declaring iterators
- Line 471: use auto when initializing with new to avoid duplicating the type name
- Line 494: use auto when declaring iterators
- Line 521: use auto when initializing with new to avoid duplicating the type name
- Line 544: use auto when declaring iterators
include/oksutils/oks/access.hpp
Errors
- Line 0: The standard copyright message wasn't found.
- Line 8: #ifndef header guard has wrong style, please use: OKSUTILS_INCLUDE_OKSUTILS_OKS_ACCESS_HPP_
- Line 34: #endif line should be "#endif // OKSUTILS_INCLUDE_OKSUTILS_OKS_ACCESS_HPP_"
- Line 29: Add #include
for string
include/oksutils/oks/ral.hpp
Errors
- Line 0: The standard copyright message wasn't found.
- Line 342: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 344: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 8: #ifndef header guard has wrong style, please use: OKSUTILS_INCLUDE_OKSUTILS_OKS_RAL_HPP_
- Line 346: #endif line should be "#endif // OKSUTILS_INCLUDE_OKSUTILS_OKS_RAL_HPP_"
- Line 15: Found other header after system header. Should be: ral.hh, other non-system headers, system headers.
- Line 19: "cout" should not be used for output in DUNE DAQ software.
- Line 19: #define appears to be used. Macros should generally be avoided if there's an alternative to them.
- Line 20: "cout" should not be used for output in DUNE DAQ software.
- Line 20: #define appears to be used. Macros should generally be avoided if there's an alternative to them.
- Line 21: "cout" should not be used for output in DUNE DAQ software.
- Line 21: #define appears to be used. Macros should generally be avoided if there's an alternative to them.
- Line 22: "cout" should not be used for output in DUNE DAQ software.
- Line 22: #define appears to be used. Macros should generally be avoided if there's an alternative to them.
- Line 23: "cout" should not be used for output in DUNE DAQ software.
- Line 23: #define appears to be used. Macros should generally be avoided if there's an alternative to them.
- Line 30: Namespace should be terminated with '// namespace coral '
- Line 32: Found other header after system header. Should be: ral.hh, other non-system headers, system headers.
- Line 33: Found other header after system header. Should be: ral.hh, other non-system headers, system headers.
- Line 188: Use int16/int64/etc, rather than the C type long
- Line 231: Use int16/int64/etc, rather than the C type long
- Line 232: Use int16/int64/etc, rather than the C type long
- Line 233: Use int16/int64/etc, rather than the C type long
- Line 234: Use int16/int64/etc, rather than the C type long
- Line 235: Use int16/int64/etc, rather than the C type long
- Line 236: Use int16/int64/etc, rather than the C type long
- Line 279: Use int16/int64/etc, rather than the C type long
- Line 342: Namespace should be terminated with '// namespace ral '
- Line 344: Namespace should be terminated with '// namespace oks '
include/oksutils/oks/tz.hpp
Errors
- Line 0: The standard copyright message wasn't found.
- Line 8: #ifndef header guard has wrong style, please use: OKSUTILS_INCLUDE_OKSUTILS_OKS_TZ_HPP_
- Line 75: #endif line should be "#endif // OKSUTILS_INCLUDE_OKSUTILS_OKS_TZ_HPP_"
- Line 67: An unsigned integer appears to be used here.
- Line 72: Namespace should be terminated with '// namespace tz '
- Line 73: Namespace should be terminated with '// namespace oks '
src/lib/oks_access.cpp
Errors
- Line 0: The standard copyright message wasn't found.
- Line 20: Namespace should be terminated with '// namespace dunedaq '
- Line 16: Add #include
for string
Warnings
- Line 13: nested namespaces can be concatenated
src/lib/oks_tz.cpp
Errors
- Line 0: The standard copyright message wasn't found.
- Line 107: An unsigned integer appears to be used here.
- Line 60: Add #include
for vector<>
Warnings
- Line 17: nested namespaces can be concatenated
test/apps/alloc.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 32: Use of reinterpret_cast can be dangerous. If there's no way to avoid its use add " // NOLINT" to the end of this line so this script will ignore it next time
- Line 43: Use of reinterpret_cast can be dangerous. If there's no way to avoid its use add " // NOLINT" to the end of this line so this script will ignore it next time
- Line 67: "cout" should not be used for output in DUNE DAQ software.
- Line 77: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 79: "cout" should not be used for output in DUNE DAQ software.
- Line 90: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 92: "cout" should not be used for output in DUNE DAQ software.
- Line 103: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 105: "cout" should not be used for output in DUNE DAQ software.
- Line 109: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 110: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 111: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 115: "cout" should not be used for output in DUNE DAQ software.
- Line 126: "cout" should not be used for output in DUNE DAQ software.
- Line 139: "cout" should not be used for output in DUNE DAQ software.
- Line 152: "cout" should not be used for output in DUNE DAQ software.
Warnings
- Line 21: private field 'i' is not used
- Line 22: private field 'p' is not used
- Line 32: do not use reinterpret_cast
- Line 43: do not use reinterpret_cast
- Line 55: variable 'count' is not initialized
- Line 58: use auto when initializing with new to avoid duplicating the type name
- Line 59: use auto when initializing with new to avoid duplicating the type name
- Line 62: do not use pointer arithmetic
- Line 62: use nullptr
- Line 63: do not use pointer arithmetic
- Line 63: use nullptr
- Line 64: do not use pointer arithmetic
- Line 64: use nullptr
- Line 74: do not use pointer arithmetic
- Line 77: do not use pointer arithmetic
- Line 79: narrowing conversion from 'rep' (aka 'long') to 'double'
- Line 87: do not use pointer arithmetic
- Line 90: do not use pointer arithmetic
- Line 92: narrowing conversion from 'rep' (aka 'long') to 'double'
- Line 100: do not use pointer arithmetic
- Line 103: do not use pointer arithmetic
- Line 105: narrowing conversion from 'rep' (aka 'long') to 'double'
- Line 126: narrowing conversion from 'rep' (aka 'long') to 'double'
- Line 139: narrowing conversion from 'rep' (aka 'long') to 'double'
- Line 152: narrowing conversion from 'rep' (aka 'long') to 'double'
test/apps/and_expression.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 25: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 27: Using C-style cast. Use static_cast
(...) instead - Line 28: Using C-style cast. Use static_cast
(...) instead - Line 30: "cout" should not be used for output in DUNE DAQ software.
Warnings
- Line 27: C-style casts are discouraged; use static_cast
- Line 28: C-style casts are discouraged; use static_cast
test/apps/attribute.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 16: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 17: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 18: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 19: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 20: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 21: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 22: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 32: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 25: "cout" should not be used for output in DUNE DAQ software.
- Line 39: "cout" should not be used for output in DUNE DAQ software.
- Line 44: "cout" should not be used for output in DUNE DAQ software.
- Line 48: "cout" should not be used for output in DUNE DAQ software.
- Line 53: "cerr" should not be used for output in DUNE DAQ software.
- Line 42: Add #include
for string - Line 42: Add #include
- for list<>
test/apps/class.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 17: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 18: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 19: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 20: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 41: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 42: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 44: "cout" should not be used for output in DUNE DAQ software.
- Line 50: "cerr" should not be used for output in DUNE DAQ software.
Warnings
- Line 16: use auto when initializing with new to avoid duplicating the type name
- Line 20: use nullptr
- Line 23: use auto when initializing with new to avoid duplicating the type name
- Line 33: use auto when initializing with new to avoid duplicating the type name
test/apps/comparator.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 19: "cout" should not be used for output in DUNE DAQ software.
- Line 23: "cerr" should not be used for output in DUNE DAQ software.
test/apps/data.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 13: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 20: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 15: An unsigned integer appears to be used here.
- Line 16: Using C-style cast. Use static_cast
(...) instead - Line 20: "cout" should not be used for output in DUNE DAQ software.
- Line 21: "cout" should not be used for output in DUNE DAQ software.
Warnings
- Line 15: C-style casts are discouraged; use static_cast
- Line 16: redundant cast to the same type
test/apps/generate_data.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 325: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 327: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 329: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 14: Found other header after system header. Should be: generate_data.hh, other non-system headers, system headers.
- Line 15: Found other header after system header. Should be: generate_data.hh, other non-system headers, system headers.
- Line 16: Found other header after system header. Should be: generate_data.hh, other non-system headers, system headers.
- Line 17: Found other header after system header. Should be: generate_data.hh, other non-system headers, system headers.
- Line 18: Found other header after system header. Should be: generate_data.hh, other non-system headers, system headers.
- Line 37: Use int16/int64/etc, rather than the C type long
- Line 43: Use int16/int64/etc, rather than the C type long
- Line 45: "cout" should not be used for output in DUNE DAQ software.
- Line 47: Using C-style cast. Use static_cast
(...) instead - Line 57: Use int16/int64/etc, rather than the C type long
- Line 58: Use int16/int64/etc, rather than the C type long
- Line 59: Use int16/int64/etc, rather than the C type long
- Line 60: Use int16/int64/etc, rather than the C type long
- Line 61: Use int16/int64/etc, rather than the C type long
- Line 62: Use int16/int64/etc, rather than the C type long
- Line 63: Use int16/int64/etc, rather than the C type long
- Line 64: Use int16/int64/etc, rather than the C type long
- Line 65: Use int16/int64/etc, rather than the C type long
- Line 76: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 76: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 77: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 77: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 78: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 78: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 79: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 79: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 122: "cout" should not be used for output in DUNE DAQ software.
- Line 215: "cout" should not be used for output in DUNE DAQ software.
- Line 217: Using C-style cast. Use static_cast
(...) instead - Line 219: An unsigned integer appears to be used here.
- Line 219: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 226: "cout" should not be used for output in DUNE DAQ software.
- Line 230: Using C-style cast. Use static_cast
(...) instead - Line 233: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 249: Using C-style cast. Use static_cast
(...) instead - Line 252: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 271: "cout" should not be used for output in DUNE DAQ software.
- Line 276: Using C-style cast. Use static_cast
(...) instead - Line 278: Using C-style cast. Use static_cast
(...) instead - Line 280: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 286: "cout" should not be used for output in DUNE DAQ software.
- Line 289: Using C-style cast. Use static_cast
(...) instead - Line 290: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 296: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 311: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 313: Using C-style cast. Use static_cast
(...) instead - Line 313: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 319: "cout" should not be used for output in DUNE DAQ software.
- Line 322: Using C-style cast. Use static_cast
(...) instead - Line 323: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 326: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 328: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 330: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 332: "cout" should not be used for output in DUNE DAQ software.
- Line 335: "cout" should not be used for output in DUNE DAQ software.
- Line 340: "cout" should not be used for output in DUNE DAQ software.
- Line 342: Using C-style cast. Use static_cast
(...) instead - Line 345: Use int16/int64/etc, rather than the C type long
- Line 351: Using C-style cast. Use static_cast
(...) instead - Line 351: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 353: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 363: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 383: Using C-style cast. Use static_cast
(...) instead - Line 398: Consider using rand_r(...) instead of rand(...) for improved thread safety.
- Line 437: "cout" should not be used for output in DUNE DAQ software.
- Line 446: Small and focused functions are preferred: main() has 274 non-comment lines (error triggered by exceeding 80 lines) (disable this by putting "// NOLINT" after the function's closing brace.)
- Line 22: Add #include
for string
Warnings
- Line 8: inclusion of deprecated C++ header 'stdlib.h'; consider using 'cstdlib' instead
- Line 9: inclusion of deprecated C++ header 'stdio.h'; consider using 'cstdio' instead
- Line 37: consider replacing 'unsigned long' with 'uint64'
- Line 43: consider replacing 'long' with 'int64'
- Line 43: variable 'j' is not initialized
- Line 47: C-style casts are discouraged; use static_cast
- Line 48: do not declare C-style arrays, use std::array<> instead
- Line 51: do not use pointer arithmetic
- Line 57: consider replacing 'unsigned long' with 'uint64'
- Line 58: consider replacing 'unsigned long' with 'uint64'
- Line 59: consider replacing 'unsigned long' with 'uint64'
- Line 60: consider replacing 'unsigned long' with 'uint64'
- Line 61: consider replacing 'unsigned long' with 'uint64'
- Line 62: consider replacing 'unsigned long' with 'uint64'
- Line 63: consider replacing 'unsigned long' with 'uint64'
- Line 64: consider replacing 'unsigned long' with 'uint64'
- Line 65: consider replacing 'unsigned long' with 'uint64'
- Line 70: use nullptr
- Line 71: use nullptr
- Line 74: do not use pointer arithmetic
- Line 75: do not use pointer arithmetic
- Line 76: do not use pointer arithmetic
- Line 76: 'atol' used to convert a string to an integer value, but function will not report conversion errors; consider using 'strtol' instead
- Line 76: do not use pointer arithmetic
- Line 77: do not use pointer arithmetic
- Line 77: 'atol' used to convert a string to an integer value, but function will not report conversion errors; consider using 'strtol' instead
- Line 77: do not use pointer arithmetic
- Line 78: do not use pointer arithmetic
- Line 78: do not use pointer arithmetic
- Line 79: do not use pointer arithmetic
- Line 79: do not use pointer arithmetic
- Line 109: do not declare C-style arrays, use std::array<> instead
- Line 117: use nullptr
- Line 148: use auto when initializing with new to avoid duplicating the type name
- Line 149: use auto when initializing with new to avoid duplicating the type name
- Line 150: use auto when initializing with new to avoid duplicating the type name
- Line 151: use auto when initializing with new to avoid duplicating the type name
- Line 152: use auto when initializing with new to avoid duplicating the type name
- Line 153: use auto when initializing with new to avoid duplicating the type name
- Line 154: use auto when initializing with new to avoid duplicating the type name
- Line 217: C-style casts are discouraged; use static_cast
- Line 218: do not use pointer arithmetic
- Line 219: C-style casts are discouraged; use static_cast
- Line 219: rand() has limited randomness; use C++11 random library instead
- Line 230: C-style casts are discouraged; use static_cast
- Line 233: C-style casts are discouraged; use static_cast
- Line 233: rand() has limited randomness; use C++11 random library instead
- Line 241: do not use pointer arithmetic
- Line 249: C-style casts are discouraged; use static_cast
- Line 252: C-style casts are discouraged; use static_cast
- Line 252: rand() has limited randomness; use C++11 random library instead
- Line 260: do not use pointer arithmetic
- Line 273: multiple declarations in a single statement reduces readability
- Line 273: variable 'i' is not initialized
- Line 273: variable 'j' is not initialized
- Line 273: variable 'j2' is not initialized
- Line 276: C-style casts are discouraged; use static_cast
- Line 277: narrowing conversion from 'unsigned long' to signed type 'int' is implementation-defined
- Line 278: C-style casts are discouraged; use static_cast
- Line 280: rand() has limited randomness; use C++11 random library instead
- Line 283: do not use pointer arithmetic
- Line 283: do not use pointer arithmetic
- Line 284: do not use pointer arithmetic
- Line 284: do not use pointer arithmetic
- Line 289: C-style casts are discouraged; use static_cast
- Line 290: rand() has limited randomness; use C++11 random library instead
- Line 290: narrowing conversion from 'unsigned long' to signed type 'int' is implementation-defined
- Line 292: do not use pointer arithmetic
- Line 292: do not use pointer arithmetic
- Line 293: do not use pointer arithmetic
- Line 296: rand() has limited randomness; use C++11 random library instead
- Line 296: narrowing conversion from 'unsigned long' to signed type 'int' is implementation-defined
- Line 297: do not use pointer arithmetic
- Line 301: do not use pointer arithmetic
- Line 301: do not use pointer arithmetic
- Line 302: do not use pointer arithmetic
- Line 302: do not use pointer arithmetic
- Line 303: do not use pointer arithmetic
- Line 303: do not use pointer arithmetic
- Line 305: do not use pointer arithmetic
- Line 305: do not use pointer arithmetic
- Line 306: do not use pointer arithmetic
- Line 306: do not use pointer arithmetic
- Line 308: do not use pointer arithmetic
- Line 309: do not use pointer arithmetic
- Line 311: rand() has limited randomness; use C++11 random library instead
- Line 311: narrowing conversion from 'unsigned long' to signed type 'int' is implementation-defined
- Line 313: C-style casts are discouraged; use static_cast
- Line 315: do not use pointer arithmetic
- Line 315: do not use pointer arithmetic
- Line 316: do not use pointer arithmetic
- Line 316: do not use pointer arithmetic
- Line 317: do not use pointer arithmetic
- Line 322: C-style casts are discouraged; use static_cast
- Line 323: rand() has limited randomness; use C++11 random library instead
- Line 326: do not use pointer arithmetic
- Line 326: rand() has limited randomness; use C++11 random library instead
- Line 326: do not use pointer arithmetic
- Line 328: do not use pointer arithmetic
- Line 328: rand() has limited randomness; use C++11 random library instead
- Line 328: do not use pointer arithmetic
- Line 330: do not use pointer arithmetic
- Line 330: rand() has limited randomness; use C++11 random library instead
- Line 330: do not use pointer arithmetic
- Line 338: variable 'i' is not initialized
- Line 342: C-style casts are discouraged; use static_cast
- Line 343: do not declare C-style arrays, use std::array<> instead
- Line 345: C-style casts are discouraged; use static_cast
- Line 345: rand() has limited randomness; use C++11 random library instead
- Line 351: redundant cast to the same type
- Line 351: rand() has limited randomness; use C++11 random library instead
- Line 363: rand() has limited randomness; use C++11 random library instead
- Line 368: do not use pointer arithmetic
- Line 369: do not use pointer arithmetic
- Line 370: do not use pointer arithmetic
- Line 371: do not use pointer arithmetic
- Line 372: do not use pointer arithmetic
- Line 373: do not use pointer arithmetic
- Line 374: do not use pointer arithmetic
- Line 383: C-style casts are discouraged; use static_cast
- Line 384: do not declare C-style arrays, use std::array<> instead
- Line 385: do not use pointer arithmetic
- Line 391: rand() has limited randomness; use C++11 random library instead
- Line 398: rand() has limited randomness; use C++11 random library instead
- Line 403: do not use pointer arithmetic
- Line 404: do not use pointer arithmetic
- Line 405: do not use pointer arithmetic
- Line 406: do not use pointer arithmetic
- Line 437: narrowing conversion from 'rep' (aka 'long') to 'double'
test/apps/index.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 50: Using C-style cast. Use static_cast
(...) instead - Line 59: Using deprecated casting style. Use static_cast
(...) instead - Line 66: "cout" should not be used for output in DUNE DAQ software.
- Line 67: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 72: "cerr" should not be used for output in DUNE DAQ software.
- Line 47: Add #include
for string - Line 60: Add #include
- for list<>
Warnings
- Line 13: inclusion of deprecated C++ header 'stdlib.h'; consider using 'cstdlib' instead
- Line 30: use auto when initializing with new to avoid duplicating the type name
- Line 33: use auto when initializing with new to avoid duplicating the type name
- Line 49: use auto when initializing with new to avoid duplicating the type name
- Line 50: C-style casts are discouraged; use static_cast
- Line 50: C-style casts are discouraged; use static_cast
- Line 59: redundant cast to the same type
test/apps/kernel.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 19: "cout" should not be used for output in DUNE DAQ software.
- Line 21: "cout" should not be used for output in DUNE DAQ software.
Warnings
- Line 17: do not use pointer arithmetic
- Line 20: use auto when declaring iterators
test/apps/method.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 13: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 14: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 20: "cout" should not be used for output in DUNE DAQ software.
- Line 29: "cout" should not be used for output in DUNE DAQ software.
test/apps/not_expression.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 23: Use int16/int64/etc, rather than the C type short
- Line 25: "cout" should not be used for output in DUNE DAQ software.
Warnings
- Line 23: C-style casts are discouraged; use static_cast
- Line 23: consider replacing 'unsigned short' with 'uint16'
test/apps/object.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 42: "cout" should not be used for output in DUNE DAQ software.
- Line 46: "cerr" should not be used for output in DUNE DAQ software.
Warnings
- Line 23: use auto when initializing with new to avoid duplicating the type name
- Line 26: use auto when initializing with new to avoid duplicating the type name
- Line 29: use auto when initializing with new to avoid duplicating the type name
- Line 36: use auto when initializing with new to avoid duplicating the type name
test/apps/or_expression.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 25: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 27: Using C-style cast. Use static_cast
(...) instead - Line 28: Using C-style cast. Use static_cast
(...) instead - Line 30: "cout" should not be used for output in DUNE DAQ software.
Warnings
- Line 27: C-style casts are discouraged; use static_cast
- Line 28: C-style casts are discouraged; use static_cast
test/apps/profiler.cxx
Errors
- Line 0: The standard copyright message wasn't found.
Warnings
- Line 18: do not use pointer arithmetic
- Line 19: do not use pointer arithmetic
test/apps/query.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 17: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 20: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 21: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 23: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 26: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 31: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 36: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 37: An unsigned integer appears to be used here.
- Line 39: An unsigned integer appears to be used here.
- Line 41: An unsigned integer appears to be used here.
- Line 44: Use int16/int64/etc, rather than the C type short
- Line 48: "cout" should not be used for output in DUNE DAQ software.
- Line 55: "cout" should not be used for output in DUNE DAQ software.
- Line 55: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 58: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 66: "cerr" should not be used for output in DUNE DAQ software.
- Line 46: Add #include
- for list<>
Warnings
- Line 24: use auto when initializing with new to avoid duplicating the type name
- Line 27: use auto when initializing with new to avoid duplicating the type name
- Line 32: use auto when initializing with new to avoid duplicating the type name
- Line 33: use auto when initializing with new to avoid duplicating the type name
- Line 34: use auto when initializing with new to avoid duplicating the type name
- Line 37: C-style casts are discouraged; use static_cast
- Line 39: C-style casts are discouraged; use static_cast
- Line 41: C-style casts are discouraged; use static_cast
- Line 44: C-style casts are discouraged; use static_cast
- Line 44: consider replacing 'unsigned short' with 'uint16'
test/apps/r_expression.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 34: "cout" should not be used for output in DUNE DAQ software.
test/apps/relationship.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 15: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 16: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 17: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 18: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 19: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 20: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 21: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 22: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 25: "cout" should not be used for output in DUNE DAQ software.
- Line 29: "cerr" should not be used for output in DUNE DAQ software.
test/apps/test_indexies.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 11: Found other header after system header. Should be: test_indexies.hh, other non-system headers, system headers.
- Line 12: Found other header after system header. Should be: test_indexies.hh, other non-system headers, system headers.
- Line 13: Found other header after system header. Should be: test_indexies.hh, other non-system headers, system headers.
- Line 14: Found other header after system header. Should be: test_indexies.hh, other non-system headers, system headers.
- Line 15: Found other header after system header. Should be: test_indexies.hh, other non-system headers, system headers.
- Line 22: "cerr" should not be used for output in DUNE DAQ software.
- Line 73: "cout" should not be used for output in DUNE DAQ software.
- Line 91: "cerr" should not be used for output in DUNE DAQ software.
- Line 97: "cerr" should not be used for output in DUNE DAQ software.
- Line 104: "cerr" should not be used for output in DUNE DAQ software.
- Line 111: "cerr" should not be used for output in DUNE DAQ software.
- Line 121: "cout" should not be used for output in DUNE DAQ software.
- Line 129: "cout" should not be used for output in DUNE DAQ software.
- Line 134: If an else has a brace on one side, it should have it on both
- Line 137: "cout" should not be used for output in DUNE DAQ software.
- Line 142: If an else has a brace on one side, it should have it on both
- Line 145: "cout" should not be used for output in DUNE DAQ software.
- Line 150: If an else has a brace on one side, it should have it on both
- Line 153: "cout" should not be used for output in DUNE DAQ software.
- Line 158: If an else has a brace on one side, it should have it on both
- Line 161: "cout" should not be used for output in DUNE DAQ software.
- Line 166: If an else has a brace on one side, it should have it on both
- Line 170: "cout" should not be used for output in DUNE DAQ software.
- Line 175: If an else has a brace on one side, it should have it on both
- Line 179: "cout" should not be used for output in DUNE DAQ software.
- Line 184: If an else has a brace on one side, it should have it on both
- Line 188: "cout" should not be used for output in DUNE DAQ software.
- Line 193: If an else has a brace on one side, it should have it on both
- Line 197: "cout" should not be used for output in DUNE DAQ software.
- Line 202: If an else has a brace on one side, it should have it on both
- Line 206: "cout" should not be used for output in DUNE DAQ software.
- Line 211: If an else has a brace on one side, it should have it on both
- Line 215: "cout" should not be used for output in DUNE DAQ software.
- Line 220: If an else has a brace on one side, it should have it on both
- Line 224: "cout" should not be used for output in DUNE DAQ software.
- Line 229: If an else has a brace on one side, it should have it on both
- Line 233: "cout" should not be used for output in DUNE DAQ software.
- Line 238: If an else has a brace on one side, it should have it on both
- Line 242: "cout" should not be used for output in DUNE DAQ software.
- Line 247: If an else has a brace on one side, it should have it on both
- Line 251: "cout" should not be used for output in DUNE DAQ software.
- Line 256: If an else has a brace on one side, it should have it on both
- Line 260: "cout" should not be used for output in DUNE DAQ software.
- Line 265: If an else has a brace on one side, it should have it on both
- Line 269: "cout" should not be used for output in DUNE DAQ software.
- Line 274: If an else has a brace on one side, it should have it on both
- Line 278: "cout" should not be used for output in DUNE DAQ software.
- Line 283: If an else has a brace on one side, it should have it on both
- Line 287: "cout" should not be used for output in DUNE DAQ software.
- Line 292: If an else has a brace on one side, it should have it on both
- Line 296: "cout" should not be used for output in DUNE DAQ software.
- Line 301: If an else has a brace on one side, it should have it on both
- Line 305: "cout" should not be used for output in DUNE DAQ software.
- Line 310: If an else has a brace on one side, it should have it on both
- Line 314: "cout" should not be used for output in DUNE DAQ software.
- Line 319: If an else has a brace on one side, it should have it on both
- Line 323: "cout" should not be used for output in DUNE DAQ software.
- Line 328: If an else has a brace on one side, it should have it on both
- Line 329: "cerr" should not be used for output in DUNE DAQ software.
- Line 334: "cout" should not be used for output in DUNE DAQ software.
- Line 348: "cout" should not be used for output in DUNE DAQ software.
- Line 349: "cout" should not be used for output in DUNE DAQ software.
- Line 350: "cout" should not be used for output in DUNE DAQ software.
- Line 352: "cout" should not be used for output in DUNE DAQ software.
- Line 354: "cout" should not be used for output in DUNE DAQ software.
- Line 355: "cout" should not be used for output in DUNE DAQ software.
- Line 357: "cout" should not be used for output in DUNE DAQ software.
- Line 358: "cout" should not be used for output in DUNE DAQ software.
- Line 360: "cout" should not be used for output in DUNE DAQ software.
- Line 361: "cout" should not be used for output in DUNE DAQ software.
- Line 362: "cout" should not be used for output in DUNE DAQ software.
- Line 364: "cout" should not be used for output in DUNE DAQ software.
- Line 369: "cout" should not be used for output in DUNE DAQ software.
- Line 370: "cout" should not be used for output in DUNE DAQ software.
- Line 372: "cout" should not be used for output in DUNE DAQ software.
- Line 375: "cout" should not be used for output in DUNE DAQ software.
- Line 378: "cout" should not be used for output in DUNE DAQ software.
- Line 379: "cout" should not be used for output in DUNE DAQ software.
- Line 380: "cout" should not be used for output in DUNE DAQ software.
- Line 382: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 385: "cout" should not be used for output in DUNE DAQ software.
- Line 387: "cout" should not be used for output in DUNE DAQ software.
- Line 390: "cerr" should not be used for output in DUNE DAQ software.
- Line 395: Small and focused functions are preferred: main() has 279 non-comment lines (error triggered by exceeding 80 lines) (disable this by putting "// NOLINT" after the function's closing brace.)
- Line 374: Add #include
for string
Warnings
- Line 9: inclusion of deprecated C++ header 'stdlib.h'; consider using 'cstdlib' instead
- Line 58: do not use pointer arithmetic
- Line 60: do not use pointer arithmetic
- Line 65: do not use pointer arithmetic
- Line 66: do not use pointer arithmetic
- Line 72: do not use pointer arithmetic
- Line 74: do not use pointer arithmetic
- Line 85: do not use pointer arithmetic
- Line 86: do not use pointer arithmetic
- Line 87: do not use pointer arithmetic
- Line 88: do not use pointer arithmetic
- Line 90: use nullptr
- Line 96: use nullptr
- Line 117: do not use pointer arithmetic
- Line 123: use nullptr
- Line 124: multiple declarations in a single statement reduces readability
- Line 126: do not use pointer arithmetic
- Line 127: do not use pointer arithmetic
- Line 131: do not use pointer arithmetic
- Line 134: do not use pointer arithmetic
- Line 135: do not use pointer arithmetic
- Line 139: do not use pointer arithmetic
- Line 142: do not use pointer arithmetic
- Line 143: do not use pointer arithmetic
- Line 147: do not use pointer arithmetic
- Line 150: do not use pointer arithmetic
- Line 151: do not use pointer arithmetic
- Line 155: do not use pointer arithmetic
- Line 158: do not use pointer arithmetic
- Line 159: do not use pointer arithmetic
- Line 163: do not use pointer arithmetic
- Line 166: do not use pointer arithmetic
- Line 167: do not use pointer arithmetic
- Line 168: do not use pointer arithmetic
- Line 172: do not use pointer arithmetic
- Line 175: do not use pointer arithmetic
- Line 176: do not use pointer arithmetic
- Line 177: do not use pointer arithmetic
- Line 181: do not use pointer arithmetic
- Line 184: do not use pointer arithmetic
- Line 185: do not use pointer arithmetic
- Line 186: do not use pointer arithmetic
- Line 190: do not use pointer arithmetic
- Line 193: do not use pointer arithmetic
- Line 194: do not use pointer arithmetic
- Line 195: do not use pointer arithmetic
- Line 199: do not use pointer arithmetic
- Line 202: do not use pointer arithmetic
- Line 203: do not use pointer arithmetic
- Line 204: do not use pointer arithmetic
- Line 208: do not use pointer arithmetic
- Line 211: do not use pointer arithmetic
- Line 212: do not use pointer arithmetic
- Line 213: do not use pointer arithmetic
- Line 217: do not use pointer arithmetic
- Line 220: do not use pointer arithmetic
- Line 221: do not use pointer arithmetic
- Line 222: do not use pointer arithmetic
- Line 226: do not use pointer arithmetic
- Line 229: do not use pointer arithmetic
- Line 230: do not use pointer arithmetic
- Line 231: do not use pointer arithmetic
- Line 235: do not use pointer arithmetic
- Line 238: do not use pointer arithmetic
- Line 239: do not use pointer arithmetic
- Line 240: do not use pointer arithmetic
- Line 244: do not use pointer arithmetic
- Line 247: do not use pointer arithmetic
- Line 248: do not use pointer arithmetic
- Line 249: do not use pointer arithmetic
- Line 253: do not use pointer arithmetic
- Line 256: do not use pointer arithmetic
- Line 257: do not use pointer arithmetic
- Line 258: do not use pointer arithmetic
- Line 262: do not use pointer arithmetic
- Line 265: do not use pointer arithmetic
- Line 266: do not use pointer arithmetic
- Line 267: do not use pointer arithmetic
- Line 271: do not use pointer arithmetic
- Line 274: do not use pointer arithmetic
- Line 275: do not use pointer arithmetic
- Line 276: do not use pointer arithmetic
- Line 280: do not use pointer arithmetic
- Line 283: do not use pointer arithmetic
- Line 284: do not use pointer arithmetic
- Line 285: do not use pointer arithmetic
- Line 289: do not use pointer arithmetic
- Line 292: do not use pointer arithmetic
- Line 293: do not use pointer arithmetic
- Line 294: do not use pointer arithmetic
- Line 298: do not use pointer arithmetic
- Line 301: do not use pointer arithmetic
- Line 302: do not use pointer arithmetic
- Line 303: do not use pointer arithmetic
- Line 307: do not use pointer arithmetic
- Line 310: do not use pointer arithmetic
- Line 311: do not use pointer arithmetic
- Line 312: do not use pointer arithmetic
- Line 316: do not use pointer arithmetic
- Line 319: do not use pointer arithmetic
- Line 320: do not use pointer arithmetic
- Line 321: do not use pointer arithmetic
- Line 325: do not use pointer arithmetic
- Line 329: do not use pointer arithmetic
- Line 336: use auto when declaring iterators
- Line 338: multiple declarations in a single statement reduces readability
test/apps/time_tests.cxx
Errors
- Line 0: The standard copyright message wasn't found.
- Line 123: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 934: C-style comment syntax detected; please use either C++ style "//" or Doxygen style
- Line 15: Found other header after system header. Should be: time_tests.hh, other non-system headers, system headers.
- Line 16: Found other header after system header. Should be: time_tests.hh, other non-system headers, system headers.
- Line 17: Found other header after system header. Should be: time_tests.hh, other non-system headers, system headers.
- Line 18: Found other header after system header. Should be: time_tests.hh, other non-system headers, system headers.
- Line 19: Found other header after system header. Should be: time_tests.hh, other non-system headers, system headers.
- Line 20: Found other header after system header. Should be: time_tests.hh, other non-system headers, system headers.
- Line 33: You don't need a ; after a }
- Line 58: "cout" should not be used for output in DUNE DAQ software.
- Line 58: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 83: #define appears to be used. Macros should generally be avoided if there's an alternative to them.
- Line 85: Use int16/int64/etc, rather than the C type long
- Line 89: #define appears to be used. Macros should generally be avoided if there's an alternative to them.
- Line 92: "cout" should not be used for output in DUNE DAQ software.
- Line 93: "cout" should not be used for output in DUNE DAQ software.
- Line 94: Using C-style cast. Use static_cast
(...) instead - Line 109: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 109: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 111: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 111: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 113: "cerr" should not be used for output in DUNE DAQ software.
- Line 144: Use int16/int64/etc, rather than the C type short
- Line 145: Using C-style cast. Use static_cast
(...) instead - Line 157: Using C-style cast. Use static_cast
(...) instead - Line 160: "cout" should not be used for output in DUNE DAQ software.
- Line 267: Use int16/int64/etc, rather than the C type long
- Line 268: Use int16/int64/etc, rather than the C type long
- Line 270: Use int16/int64/etc, rather than the C type long
- Line 276: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 294: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 309: Use int16/int64/etc, rather than the C type long
- Line 316: Increment/decrement operator should appear alone on its line unless in a while/for loop head
- Line 565: Use int16/int64/etc, rather than the C type long
- Line 566: Use int16/int64/etc, rather than the C type long
- Line 582: Use int16/int64/etc, rather than the C type long
- Line 601: Use int16/int64/etc, rather than the C type long
- Line 606: Use int16/int64/etc, rather than the C type long
- Line 607: Use int16/int64/etc, rather than the C type long
- Line 609: "cout" should not be used for output in DUNE DAQ software.
- Line 614: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 633: "cout" should not be used for output in DUNE DAQ software.
- Line 639: Use int16/int64/etc, rather than the C type long
- Line 652: If/else bodies with multiple statements require braces
- Line 652: "cerr" should not be used for output in DUNE DAQ software.
- Line 664: Use int16/int64/etc, rather than the C type long
- Line 679: If/else bodies with multiple statements require braces
- Line 679: "cerr" should not be used for output in DUNE DAQ software.
- Line 691: Use int16/int64/etc, rather than the C type long
- Line 704: "cerr" should not be used for output in DUNE DAQ software.
- Line 728: Use int16/int64/etc, rather than the C type long
- Line 729: Use int16/int64/etc, rather than the C type long
- Line 731: Use int16/int64/etc, rather than the C type long
- Line 748: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 753: "cout" should not be used for output in DUNE DAQ software.
- Line 769: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 774: "cout" should not be used for output in DUNE DAQ software.
- Line 790: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 795: "cout" should not be used for output in DUNE DAQ software.
- Line 813: Using C-style cast. Use static_cast
(...) instead - Line 813: Use int16/int64/etc, rather than the C type long
- Line 830: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 835: "cout" should not be used for output in DUNE DAQ software.
- Line 852: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 857: "cout" should not be used for output in DUNE DAQ software.
- Line 878: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 883: "cout" should not be used for output in DUNE DAQ software.
- Line 889: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 919: "cout" should not be used for output in DUNE DAQ software.
- Line 924: "cout" should not be used for output in DUNE DAQ software.
- Line 925: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 938: "cout" should not be used for output in DUNE DAQ software.
- Line 943: "cout" should not be used for output in DUNE DAQ software.
- Line 944: The delete operator appears to be used; owning memory should be done with a smart pointer rather than a raw pointer
- Line 948: Small and focused functions are preferred: main() has 504 non-comment lines (error triggered by exceeding 80 lines) (disable this by putting "// NOLINT" after the function's closing brace.)
- Line 342: Add #include
for string - Line 726: Add #include
- for list<>
Warnings
- Line 8: inclusion of deprecated C++ header 'stdio.h'; consider using 'cstdio' instead
- Line 9: inclusion of deprecated C++ header 'stdlib.h'; consider using 'cstdlib' instead
- Line 10: inclusion of deprecated C++ header 'math.h'; consider using 'cmath' instead
- Line 83: function-like macro 'TIME_TEST_START' used; consider a 'constexpr' template function
- Line 87: macro argument should be enclosed in parentheses
- Line 89: function-like macro 'TIME_TEST_STOP' used; consider a 'constexpr' template function
- Line 103: use nullptr
- Line 104: use nullptr
- Line 108: do not use pointer arithmetic
- Line 109: do not use pointer arithmetic
- Line 110: do not use pointer arithmetic
- Line 111: do not use pointer arithmetic
- Line 113: do not use pointer arithmetic
- Line 143: use auto when initializing with new to avoid duplicating the type name
- Line 144: use auto when initializing with new to avoid duplicating the type name
- Line 144: C-style casts are discouraged; use static_cast
- Line 144: consider replacing 'short' with 'int16'
- Line 145: use auto when initializing with new to avoid duplicating the type name
- Line 145: C-style casts are discouraged; use static_cast
- Line 146: use auto when initializing with new to avoid duplicating the type name
- Line 147: use auto when initializing with new to avoid duplicating the type name
- Line 157: C-style casts are discouraged; use static_cast
- Line 157: C-style casts are discouraged; use static_cast
- Line 157: narrowing conversion from 'rep' (aka 'long') to 'double'
- Line 165: use nullptr
- Line 183: use nullptr
- Line 233: use nullptr
- Line 234: use nullptr
- Line 235: use nullptr
- Line 267: consider replacing 'unsigned long' with 'uint64'
- Line 268: consider replacing 'unsigned long' with 'uint64'
- Line 269: use auto when initializing with new to avoid duplicating the type name
- Line 270: consider replacing 'unsigned long' with 'uint64'
- Line 275: use auto when declaring iterators
- Line 277: do not use pointer arithmetic
- Line 287: do not use pointer arithmetic
- Line 287: do not use pointer arithmetic
- Line 292: narrowing conversion from 'unsigned long' to 'double'
- Line 308: variable 'd' is not initialized
- Line 309: consider replacing 'unsigned long' with 'uint64'
- Line 310: use auto when initializing with new to avoid duplicating the type name
- Line 315: use auto when declaring iterators
- Line 316: do not use pointer arithmetic
- Line 358: do not use pointer arithmetic
- Line 359: do not use pointer arithmetic
- Line 360: do not use pointer arithmetic
- Line 361: do not use pointer arithmetic
- Line 362: do not use pointer arithmetic
- Line 363: do not use pointer arithmetic
- Line 364: do not use pointer arithmetic
- Line 370: narrowing conversion from 'unsigned long' to 'double'
- Line 383: do not use pointer arithmetic
- Line 384: do not use pointer arithmetic
- Line 385: do not use pointer arithmetic
- Line 386: do not use pointer arithmetic
- Line 387: do not use pointer arithmetic
- Line 388: do not use pointer arithmetic
- Line 389: do not use pointer arithmetic
- Line 395: narrowing conversion from 'unsigned long' to 'double'
- Line 410: do not use pointer arithmetic
- Line 411: do not use pointer arithmetic
- Line 412: do not use pointer arithmetic
- Line 418: narrowing conversion from 'unsigned long' to 'double'
- Line 431: do not use pointer arithmetic
- Line 432: do not use pointer arithmetic
- Line 433: do not use pointer arithmetic
- Line 439: narrowing conversion from 'unsigned long' to 'double'
- Line 449: C-style casts are discouraged; use static_cast
- Line 462: do not use pointer arithmetic
- Line 463: do not use pointer arithmetic
- Line 464: do not use pointer arithmetic
- Line 465: do not use pointer arithmetic
- Line 466: do not use pointer arithmetic
- Line 467: do not use pointer arithmetic
- Line 468: do not use pointer arithmetic
- Line 473: narrowing conversion from 'unsigned long' to 'double'
- Line 485: do not use pointer arithmetic
- Line 486: do not use pointer arithmetic
- Line 488: do not use pointer arithmetic
- Line 489: do not use pointer arithmetic
- Line 491: do not use pointer arithmetic
- Line 492: do not use pointer arithmetic
- Line 497: narrowing conversion from 'unsigned long' to 'double'
- Line 510: do not use pointer arithmetic
- Line 511: do not use pointer arithmetic
- Line 512: do not use pointer arithmetic
- Line 513: do not use pointer arithmetic
- Line 514: do not use pointer arithmetic
- Line 515: do not use pointer arithmetic
- Line 516: do not use pointer arithmetic
- Line 521: narrowing conversion from 'unsigned long' to 'double'
- Line 534: do not use pointer arithmetic
- Line 535: do not use pointer arithmetic
- Line 537: do not use pointer arithmetic
- Line 538: do not use pointer arithmetic
- Line 540: do not use pointer arithmetic
- Line 541: do not use pointer arithmetic
- Line 546: narrowing conversion from 'unsigned long' to 'double'
- Line 565: consider replacing 'unsigned long' with 'uint64'
- Line 566: consider replacing 'unsigned long' with 'uint64'
- Line 568: do not declare C-style arrays, use std::array<> instead
- Line 581: do not declare C-style arrays, use std::array<> instead
- Line 582: C-style casts are discouraged; use static_cast
- Line 593: do not use pointer arithmetic
- Line 593: rand() has limited randomness; use C++11 random library instead
- Line 596: do not use pointer arithmetic
- Line 596: rand() has limited randomness; use C++11 random library instead
- Line 600: do not declare C-style arrays, use std::array<> instead
- Line 601: C-style casts are discouraged; use static_cast
- Line 606: consider replacing 'unsigned long' with 'uint64'
- Line 607: consider replacing 'unsigned long' with 'uint64'
- Line 623: do not declare C VLA arrays, use std::vector<> instead
- Line 623: variable length arrays in C++ are a Clang extension
- Line 639: consider replacing 'unsigned long' with 'uint64'
- Line 658: narrowing conversion from 'unsigned long' to 'double'
- Line 664: consider replacing 'unsigned long' with 'uint64'
- Line 685: narrowing conversion from 'unsigned long' to 'double'
- Line 691: consider replacing 'unsigned long' with 'uint64'
- Line 710: narrowing conversion from 'unsigned long' to 'double'
- Line 728: consider replacing 'unsigned long' with 'uint64'
- Line 729: consider replacing 'unsigned long' with 'uint64'
- Line 731: consider replacing 'unsigned long' with 'uint64'
- Line 739: C-style casts are discouraged; use static_cast (if needed, the cast may be redundant)
- Line 761: C-style casts are discouraged; use static_cast (if needed, the cast may be redundant)
- Line 782: C-style casts are discouraged; use static_cast (if needed, the cast may be redundant)
- Line 813: C-style casts are discouraged; use static_cast
- Line 813: consider replacing 'unsigned long' with 'uint64'
- Line 813: C-style casts are discouraged; use static_cast
- Line 813: C-style casts are discouraged; use static_cast
- Line 822: C-style casts are discouraged; use static_cast (if needed, the cast may be redundant)
- Line 842: C-style casts are discouraged; use static_cast (if needed, the cast may be redundant)
- Line 864: C-style casts are discouraged; use static_cast (if needed, the cast may be redundant)