I feel this needs to be re-iterated as it was not understood.
As it stands, there is absolutely no way to represent nested namespaces in
either a single nor multiple .gir files, but there is in .vapi files. When
valac generates the .gir for a nested namespace, it ignores all the
sub-namespaces
Hello,
On Tue, April 13, 2010 07:51, Arc Riley wrote:
1) Is the .gir expected to be equivalent to the .vapi, i.e. is it
supposed
to
contain all information needed to create the .vapi
No. One of the biggest feature gaps in .gir is you cannot have nested
namespaces, everything in your
1) Is the .gir expected to be equivalent to the .vapi, i.e. is it supposed
to
contain all information needed to create the .vapi
No. One of the biggest feature gaps in .gir is you cannot have nested
namespaces, everything in your .gir must exist inside the same single-level
namespace.
On 3),
3) I don't think a record should be treated as struct, because the
GLib-2.0.gir from GI repository uses that to annotate all the non-gobject
classes like IOChannel, which are reference types. So what is the correct
way to handle them? (guess I can look into glib-2.0.vapi,
Hello Folks,
I am trying to make a usable .vapi for gobject-introspection and I am seeing
that I will have to fix them manually. So I would like to ask:
1) Is the .gir expected to be equivalent to the .vapi, i.e. is it supposed to
contain all information needed to create the .vapi (if it was
