> > * larsu points out that only <glib.h> is required, not an
> > additional include for <glib-object.h>; I looked at this, and can't
> > quite grok how this chaining works as <glib.h> doesn't appear to
> > pull in any of the GObject headers?
>
> Sorry if I wasn't clear: glib-object.h includes glib.h, not the other
> way around. (glib itself doesn't depend on gobject)
Ah, I didn't think to look at the reverse! Thanks for the clarification!
> > [...] * Regarding line length... the vt130 comment was funny, but
> > not a real justification. I would suggest checking out a few public
> > C/C++ styleguides ( GTK+, Google Style Guides, ... ) for reference,
> > most if not all recommend 80 char lines.
>
> In general, I totally agree with a 80 char limit. However, the g*
> libraries have an affinity towards fairly long function names, which
> can make this hard to enforce sometimes.
Well, I'm certainly up for setting the length longer ( 100? 120? ), as
long as there's an agreed upon convention we all can abide by...
> > * larsu points out that only <glib.h> is required, not an
> > additional include for <glib-object.h>; I looked at this, and can't
> > quite grok how this chaining works as <glib.h> doesn't appear to
> > pull in any of the GObject headers?
>
> Sorry if I wasn't clear: glib-object.h includes glib.h, not the other
> way around. (glib itself doesn't depend on gobject)
Ah, I didn't think to look at the reverse! Thanks for the clarification!
> > [...] * Regarding line length... the vt130 comment was funny, but
> > not a real justification. I would suggest checking out a few public
> > C/C++ styleguides ( GTK+, Google Style Guides, ... ) for reference,
> > most if not all recommend 80 char lines.
>
> In general, I totally agree with a 80 char limit. However, the g*
> libraries have an affinity towards fairly long function names, which
> can make this hard to enforce sometimes.
Well, I'm certainly up for setting the length longer ( 100? 120? ), as
long as there's an agreed upon convention we all can abide by...
> -----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/ PIrXeAAoJEAbD1b cyW6kFyu8H/ 0wxSAHY4iEwIRUz hEkvFzFV uDmGs3QIldW1iV3 B2rTv4ZxXt3RECV UTsme0tCR7Gea+ oU81H 5QqOP4o/ tDbw3OaFoBIYfDN dCejaRjM1c6fip8 kOmtcfl2gdR qo3dFsy+ KNmEg1rHRwvjq9G VrkfJXywCylIkz6 3FIoHQijR7s 6CG5jAEU9FDcKgT g+KK622WqVWCy7B upp24LVEtdyuJO3 wuYseH2Xe9Kf dydkMHWiVR0L+ jXKuKzmoCio8p4L 0/Q//GwSuvILISn xysLU=
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://
>
> iQEcBAEBAgAGBQJ
> f/dkNSdWR9ODyOr
> 8lQKV0tP2E81g6H
> PoonUiw8D9BT6gF
> nr7hkO/
> WI0pUAODJh3CAp/
> =de0l
> -----END PGP SIGNATURE-----