Am Wed, 17 Dec 2008 15:01:55 -0500
schrieb Morten Welinder mort...@gnome.org:
Its supposed to be documented in the api docs, at the top of the
synopsis for each section. Of course, the documentation may be
outdated.
This is a farce. Why try to enforce something that does not seem to
On Wed, Dec 17, 2008 at 9:17 AM, Morten Welinder mort...@gnome.org wrote:
Someone is pushing changes to the way Gnome modules include header files,
see http://live.gnome.org/GnomeGoals/CleanupGTKIncludes
GTK+ is moving toward a model where it is only allowed to include the
'toplevel'
Cosimo Cecchi wrote:
On Wed, 2008-12-17 at 09:17 -0500, Morten Welinder wrote:
So: what header files are meant to be included by applications? Where is this
information documented?
AFAIK it's not clearly documented anywhere, but in addition to the
toplevel headers, you should always include
Its supposed to be documented in the api docs, at the top of the
synopsis for each section. Of course, the documentation may be
outdated.
This is a farce. Why try to enforce something that does not seem to
have ever been documented? At least not correctly.
On
Someone is pushing changes to the way Gnome modules include header files,
see http://live.gnome.org/GnomeGoals/CleanupGTKIncludes
GTK+ is moving toward a model where it is only allowed to include the
'toplevel'
headers. Only glib.h, gdk/gdk.h, gdk-pixbuf/gdk-pixbuf.h and gtk/gtk.h
can be
On Wed, 2008-12-17 at 09:17 -0500, Morten Welinder wrote:
So: what header files are meant to be included by applications? Where is this
information documented?
AFAIK it's not clearly documented anywhere, but in addition to the
toplevel headers, you should always include gdk/gdkkeysyms.h,
On Wed, Dec 17, 2008 at 3:01 PM, Morten Welinder mort...@gnome.org wrote:
Humble suggestion:
1. Correctly document which header files can be included by
applications. Then worry about enforcement.
2. Make sure tests and demos subdirectories follow the policy.
3. Then worry about
