Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
B
blender-dev-tools
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
blender
blender-dev-tools
Commits
bd8326cc
Commit
bd8326cc
authored
Feb 23, 2014
by
Campbell Barton
Browse files
Options
Downloads
Patches
Plain Diff
Add cc files for syntax checker
parent
01cc797d
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
check_source/check_style_c.py
+2
-1
2 additions, 1 deletion
check_source/check_style_c.py
with
2 additions
and
1 deletion
check_source/check_style_c.py
+
2
−
1
View file @
bd8326cc
...
...
@@ -965,6 +965,7 @@ def quick_check_include_guard(lines):
else
:
warning_lineonly
(
"
missing include guard %r
"
%
guard
,
1
)
def
quick_check_source
(
fp
,
code
,
args
):
global
filepath
...
...
@@ -1120,7 +1121,7 @@ def scan_source_recursive(dirpath, args):
def
is_source
(
filename
):
ext
=
splitext
(
filename
)[
1
]
return
(
ext
in
{
"
.c
"
,
"
.inl
"
,
"
.cpp
"
,
"
.cxx
"
,
"
.hpp
"
,
"
.hxx
"
,
"
.h
"
,
"
.osl
"
})
return
(
ext
in
{
"
.c
"
,
"
.inl
"
,
"
.cpp
"
,
"
.cxx
"
,
"
.cc
"
,
"
.hpp
"
,
"
.hxx
"
,
"
.h
"
,
"
.hh
"
,
"
.osl
"
})
for
filepath
in
sorted
(
source_list
(
dirpath
,
is_source
)):
if
is_ignore
(
filepath
):
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
sign in
to comment