When doing type resolution on a string, treat it as its own ctype
authorColin Walters <walters@verbum.org>
Fri, 23 Oct 2009 03:53:37 +0000 (23:53 -0400)
committerColin Walters <walters@verbum.org>
Fri, 23 Oct 2009 03:53:37 +0000 (23:53 -0400)
commit9fe8f41bacef14f08d4d30528725fa920dc7e49a
tree3971bafaf3fec71fb5251c5ed11d7de4f3fe6912
parent74823810e941aeebcdf8c87b134a14a978cbfeaa
When doing type resolution on a string, treat it as its own ctype

Calling _resolve_param_type on a string instead of Node is fairly unusual,
and (as far as I could see) basically only happened in the Array processing
code.  We were passing None as the ctype in this case, but we might as well
try using the name as a ctype too.

This fixes using GCallback (and in general any item in an array that comes
from an included gir).
giscanner/transformer.py
tests/scanner/foo-1.0-expected.gir
tests/scanner/foo-1.0-expected.tgir
tests/scanner/foo.h