GNOME Bugzilla – Bug 617107
Move invocation code to its own file
Last modified: 2010-05-03 16:25:58 UTC
.
Created attachment 159813 [details] [review] Move invocation code to its own file
Review of attachment 159813 [details] [review]: Looks good. ::: gi/pygi-callbacks.h @@ +22,2 @@ #define __PYGI_CALLBACKS_H__ +#include "pygi-closure.h" Is this change needed? Isn't pygi-closure.c imported in pygi.h?
(In reply to comment #2) > Review of attachment 159813 [details] [review]: > > Looks good. > > ::: gi/pygi-callbacks.h > @@ +22,2 @@ > #define __PYGI_CALLBACKS_H__ > +#include "pygi-closure.h" > > Is this change needed? Isn't pygi-closure.c imported in pygi.h? Well, but pygi-callbacks.h didn't import anything.
Is that a problem?
Created attachment 160185 [details] [review] Move invocation code to its own file You are right, it wasn't needed.
Review of attachment 160185 [details] [review]: Fine with me!
Attachment 160185 [details] pushed as 9669acd - Move invocation code to its own file