@@ -305,7 +305,7 @@ class SarifLogger(object):
305
305
# --- OLDFILENAME OLDTIMESTAMP
306
306
# +++ NEWFILENAME NEWTIMESTAMP
307
307
# @@ -OLDSTART,OLDLENGTH +NEWSTART,NEWLENGTH @@
308
- # ... Changes where preceding "+" is add, "-" is remove, " " is unchanged.
308
+ # ... Changes where preceeding "+" is add, "-" is remove, " " is unchanged.
309
309
#
310
310
# ",OLDLENGTH" and ",NEWLENGTH" are optional (they default to 1).
311
311
# GNU unified diff format doesn't normally output "Index:"; you use
@@ -770,7 +770,7 @@ def extract_c_parameters(text, pos=0):
770
770
# so will get confused by patterns like gettext("hi") + function("bye")
771
771
# In practice, this doesn't seem to be a problem; gettext() is usually
772
772
# wrapped around the entire parameter.
773
- # The ?s makes it possible to match multi-line strings.
773
+ # The ?s makes it posible to match multi-line strings.
774
774
gettext_pattern = re .compile (r'(?s)^\s*' 'gettext' r'\s*\((.*)\)\s*$' )
775
775
undersc_pattern = re .compile (r'(?s)^\s*' '_(T(EXT)?)?' r'\s*\((.*)\)\s*$' )
776
776
@@ -1026,7 +1026,7 @@ def c_static_array(hit):
1026
1026
1027
1027
def cpp_unsafe_stl (hit ):
1028
1028
# Use one of the overloaded classes from the STL in C++14 and higher
1029
- # instead of the <C++14 versions of these functions that did not
1029
+ # instead of the <C++14 versions of theses functions that did not
1030
1030
# if the second iterator could overflow
1031
1031
if len (hit .parameters ) <= 4 :
1032
1032
add_warning (hit )
@@ -1136,7 +1136,7 @@ c_ruleset = {
1136
1136
"lstrcpyn|wcsncpy|_tcsncpy|_mbsnbcpy" :
1137
1137
(c_buffer ,
1138
1138
1 , # Low risk level, because this is often used correctly when FIXING security
1139
- # problems, and raising it to a higher risk level would cause many false
1139
+ # problems, and raising it to a higher risk levle would cause many false
1140
1140
# positives.
1141
1141
"Easily used incorrectly; doesn't always \\ 0-terminate or "
1142
1142
"check for invalid pointers [MS-banned] (CWE-120)" ,
0 commit comments