Clean up annotation parsing, don't try to parse invalid annotations
authorColin Walters <walters@verbum.org>
Thu, 24 Jun 2010 20:39:35 +0000 (16:39 -0400)
committerColin Walters <walters@verbum.org>
Fri, 25 Jun 2010 13:19:14 +0000 (09:19 -0400)
commit0a674061eb4b7307f62c330bb3ebec5ad36ab1c6
tree6ff9e298011052ef2ecb08e55b6440b99566400d
parent11cfe386c37ced44a8e3efb5556bde3a43a11171
Clean up annotation parsing, don't try to parse invalid annotations

The old parser tried to parse:
@foo: some text here (other text)
Reject this.  We strictly require another colon at the end to parse
the text in between as (option) (other option).
Futher ensure we only attempt to do option parse if we find something
that matches the strict regexp ([A-Za-z]+).  This could be tightened
further.

TODO: Have a warning for something that looks like an annotation,
but isn't.

https://bugzilla.gnome.org/show_bug.cgi?id=622659
gir/Everything-1.0-expected.gir
gir/GIMarshallingTests-1.0-expected.gir
gir/everything.c
gir/gimarshallingtests.c
giscanner/annotationparser.py
tests/scanner/annotation-1.0-expected.gir
tests/scanner/annotation-1.0-expected.tgir
tests/scanner/annotation.c
tests/scanner/annotation.h
tests/scanner/foo-1.0-expected.gir