From 3c8c01c28a5d7ee94ec74be6c205942ddae2eb59 Mon Sep 17 00:00:00 2001 From: Dieter Verfaillie Date: Thu, 22 Nov 2012 17:58:46 +0100 Subject: [PATCH] giscanner: don't continue parsing after multiline descriptions This doesn't change anything, really, except that you don't have to read a whole page of code just to realize that nothing else happens with that line and we go on processing the next. Putting the continue statements there makes it a bit more readable. https://bugzilla.gnome.org/show_bug.cgi?id=688897 --- giscanner/annotationparser.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/giscanner/annotationparser.py b/giscanner/annotationparser.py index 393ef38..e91df3a 100644 --- a/giscanner/annotationparser.py +++ b/giscanner/annotationparser.py @@ -1086,18 +1086,18 @@ class AnnotationParser(object): elif in_part == PART_PARAMETERS: self._validate_multiline_annotation_continuation(line, original_line, column_offset, position) - # Append to parameter description. current_param.comment += ' ' + line.strip() + continue elif in_part == PART_TAGS: self._validate_multiline_annotation_continuation(line, original_line, column_offset, position) - # Append to tag description. if current_tag.name.lower() in [TAG_RETURNS, TAG_RETURNVALUE]: current_tag.comment += ' ' + line.strip() else: current_tag.value += ' ' + line.strip() + continue ######################################################################## # Finished parsing this comment block. -- 2.7.4