summaryrefslogtreecommitdiff
path: root/giscanner
diff options
context:
space:
mode:
authorDieter Verfaillie <dieterv@optionexplicit.be>2012-11-22 17:58:46 +0100
committerDieter Verfaillie <dieterv@optionexplicit.be>2012-11-28 21:31:24 +0100
commit3c8c01c28a5d7ee94ec74be6c205942ddae2eb59 (patch)
tree3a9d45a72d1936bc3c6be9b219156cbcabeceef3 /giscanner
parentc291bce772a09af1e884a064ceaa736712fe36a4 (diff)
downloadgobject-introspection-3c8c01c28a5d7ee94ec74be6c205942ddae2eb59.tar.gz
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
Diffstat (limited to 'giscanner')
-rw-r--r--giscanner/annotationparser.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/giscanner/annotationparser.py b/giscanner/annotationparser.py
index 393ef38a..e91df3ae 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.