aboutsummaryrefslogtreecommitdiff
path: root/clint.py
diff options
context:
space:
mode:
authorJohn Schmidt <john.schmidt.h@gmail.com>2014-04-09 18:44:31 +0200
committerThiago de Arruda <tpadilha84@gmail.com>2014-04-21 12:19:08 -0300
commit302998b0c76006d7461003d840e1de3c8b41a0c3 (patch)
treed4d2d3ee4dbd6b413ddfe4b80056a8a1213daaa8 /clint.py
parentc1c335f71cf7c6d95dbf7385e3c51e143ba8b2e9 (diff)
downloadrneovim-302998b0c76006d7461003d840e1de3c8b41a0c3.tar.gz
rneovim-302998b0c76006d7461003d840e1de3c8b41a0c3.tar.bz2
rneovim-302998b0c76006d7461003d840e1de3c8b41a0c3.zip
Remove dead code in clint.py
Diffstat (limited to 'clint.py')
-rwxr-xr-xclint.py24
1 files changed, 5 insertions, 19 deletions
diff --git a/clint.py b/clint.py
index e15d49c07f..d0770e913c 100755
--- a/clint.py
+++ b/clint.py
@@ -28,10 +28,10 @@
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-"""Does google-lint on c++ files.
+"""Does neovim-lint on c files.
The goal of this script is to identify places in the code that *may*
-be in non-compliance with google style. It does not attempt to fix
+be in non-compliance with neovim style. It does not attempt to fix
up these problems -- the point is to educate. It does also not
attempt to find all problems, or to ensure that everything it does
find is legitimately a problem.
@@ -65,7 +65,7 @@ Syntax: clint.py [--verbose=#] [--output=vs7] [--filter=-x,+y,...]
<file> [file] ...
The style guidelines this tries to follow are those in
- http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml
+ http://neovim.org/development-wiki/style-guide/style-guide.xml
Note: This is Google's cpplint.py modified for use with the Neovim project,
which follows the Google C++ coding convention except with the following
@@ -351,8 +351,7 @@ class _IncludeState(dict):
filename and line number on which that file was included.
Call CheckNextIncludeOrder() once for each header in the file, passing
- in the type constants defined above. Calls in an illegal order will
- raise an _IncludeError with an appropriate error message.
+ in the type constants defined above.
"""
# self._section will move monotonically through this set. If it ever
@@ -613,11 +612,6 @@ class _FunctionState(object):
self.in_a_function = False
-class _IncludeError(Exception):
- """Indicates a problem with the include order in a file."""
- pass
-
-
class FileInfo:
"""Provides utility functions for filenames.
@@ -674,14 +668,6 @@ class FileInfo:
"""File extension - text following the final period."""
return self.Split()[2]
- def NoExtension(self):
- """File has no source file extension."""
- return '/'.join(self.Split()[0:2])
-
- def IsSource(self):
- """File has a source file extension."""
- return self.Extension()[1:] == 'c'
-
def _ShouldPrintError(category, confidence, linenum):
"""If confidence >= verbose, category passes filter and is not suppressed."""
@@ -2900,7 +2886,7 @@ def ProcessFileData(filename, file_extension, lines, error,
CheckForNewlineAtEOF(filename, lines, error)
def ProcessFile(filename, vlevel, extra_check_functions=[]):
- """Does google-lint on a single file.
+ """Does neovim-lint on a single file.
Args:
filename: The name of the file to parse.