Something went wrong on our end
-
Jakub Klinkovský authored
- base class with non-virtual destructor causes undefined behaviour - missing return statements at the end of non-void functions - missing const before char* function argument - reordered initialization of class members - misleading indentation after for statement - fixed use of uninitialized variables - fixed unsequenced modification and access to variables (the C++ standard does not define the evaluation order of operands, so expressions with side-effects such as j++ cause undefined behaviour)
Jakub Klinkovský authored- base class with non-virtual destructor causes undefined behaviour - missing return statements at the end of non-void functions - missing const before char* function argument - reordered initialization of class members - misleading indentation after for statement - fixed use of uninitialized variables - fixed unsequenced modification and access to variables (the C++ standard does not define the evaluation order of operands, so expressions with side-effects such as j++ cause undefined behaviour)