On Thu, 2014-02-27 at 13:35 +0200, fr33domlover wrote: > If this is a problem, a preprocessor macro can be added to prevent that > warning. GTK seems to use GTK_COMPILATION and and __GTK_H_INSIDE__ or > something like that, which allow individual header inclusion.
I would prefer to avoid hacking around it. When we get some strange side-effect then it would be our own fault. > They could also add another switch, e.g. BINDING_COMPILATION, so > bindings can compile faster by including specific headers. > > Just an idea... or just include gtk.h everywhere, it's fine as long as > the build takes reasonable time. It's not an issue of compile time. We generally just prefer to avoid bringing in unnecessary declarations, particularly when we must include a GTK+ header in a gtkmm header. C headers are not as clean as C++ headers. But it's not an actual problem eight now. -- murr...@murrayc.com www.murrayc.com www.openismus.com _______________________________________________ gtkmm-list mailing list gtkmm-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtkmm-list
