You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: MATLAB-Coding-Guidelines.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ All guidelines of type "Rule" are assigned priority "Highly recommended" and all
54
54
Why use CC4M for checking compliance with the MATLAB Guidelines?
55
55
- Using CC4M for detecting violations comes with a coverage of over 60% of all guidelines (compared to ~30% by using the MATLAB Code Analyzer)
56
56
- CC4M runs all checks in MATLAB R2017b and newer with the note that new features (like `arguments` block) are only checked for in the releases were the feature is available.
57
-
- The Violations report includes a link to the violated guideline, making the checking process a learning experiecne as well.
57
+
- The violations report includes a link to the violated guideline, making the checking process a learning experience as well.
58
58
- Other valuable features and all available checks are described in the [documentation](https://doc.monkeyproofsolutions.nl/code-checker-for-matlab/code-checker-for-matlab/index.html).
59
59
60
60
## Deviations from original
@@ -64,7 +64,7 @@ Why use CC4M for checking compliance with the MATLAB Guidelines?
64
64
- The "Detection" section of every guideline is expanded in case CC4M can detect violations.
65
65
66
66
<!--# TODO
67
-
- Add ID to every guidelin
67
+
- Add ID to every guideline
68
68
- Update detection to also reflect the check used in CC4M
0 commit comments