GNOME Bugzilla – Bug 731547
Support renamed signals and properties
Last modified: 2018-05-22 15:11:08 UTC
When we have a signal which conflicts with a property, such as DBusConnection.closed in GIO, we currently have to choose one because renaming either will result in incorrect C being generated. AFAIK there is no annotation for property or signal names.
The behavior is to always prefer properties. What do you want to do exactly instead? Rename the signal to something else?
Yep. See bug #684358.
You should be able to rename with something like .close#signal name="foo", or .close#virtual_signal name="foo", or whatever is the tag name in the .gir.
I can, the problem is the vapi just says something like public signal void foo (); With no CCode annotation or anything to tell the compiler that the real name is "closed".
*** Bug 618930 has been marked as a duplicate of this bug. ***
*** Bug 652533 has been marked as a duplicate of this bug. ***
Created attachment 353266 [details] [review] codegen: Support renamed signals The CCode attribute 'cname' needs to be given as canonical representation as it is expected in C.
Created attachment 353277 [details] [review] codegen: Support renamed signals The CCode attribute 'cname' needs to be given as canonical representation as it is expected in C.
Comment on attachment 353277 [details] [review] codegen: Support renamed signals Attachment 353277 [details] pushed as 9bee488 - codegen: Support renamed signals
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/vala/issues/455.