Bug 574139 – There is no way to identify 'user_data' arguments in the callback signature
authorAndreas Rottmann <a.rottmann@gmx.at>
Mon, 9 Mar 2009 17:33:00 +0000 (18:33 +0100)
committerAndreas Rottmann <a.rottmann@gmx.at>
Mon, 9 Mar 2009 17:33:00 +0000 (18:33 +0100)
commit2bd97368f6ced0d23977ce980ac159453cc18d8c
tree4be7dad53ed3c482832547cf917d70ba3cb90a15
parentfdbe3cc3e1cfaa546648a76b1dca72beead0b65b
Bug 574139 – There is no way to identify 'user_data' arguments in the callback signature

Add a heuristic to the scanner that flags arguments of callbacks that
are named 'user_data' (exact match) and have a 'any (void*) type.

These arguments are marked by setting the 'closure' field of ArgBlob
to the index of themselves.

Signed-off-by: Andreas Rottmann <a.rottmann@gmx.at>
giscanner/transformer.py
tests/scanner/annotation-1.0-expected.gir
tests/scanner/annotation-1.0-expected.tgir
tests/scanner/utility-1.0-expected.gir
tests/scanner/utility-1.0-expected.tgir