On Wed, 14 Dec 2011, Eric Blake wrote: > On 12/14/2011 11:54 AM, Stefan Weil wrote: > >> It does violate the standard _ followed by upper case letter is reserved > >> in all contexts. > > > > sCamelCase instead of _CamelCase seems to work, too. > > What about _camelCase instead of _CamelCase? That preserves the leading > underscore, but no longer uses the reserved _ followed by a capital. > > At any rate, that's the convention libvirt is using; all public structs > are prefixed with vir, so things like: > > typedef struct _virConnect virConnect; > > are both parseable by gtkdocs as well as C standard compliant. > >
7.1.3 7.1.3 Reserved identifiers 1 Each header declares or defines all identifiers listed in its associated subclause, and optionally declares or defines identifiers listed in its associated future library directions subclause and identifiers which are always reserved either for any use or for use as file scope identifiers. - All identifiers that begin with an underscore and either an uppercase letter or another underscore are always reserved for any use. - All identifiers that begin with an underscore are always reserved for use as identifiers with file scope in both the ordinary and tag name spaces [..snip..] IOW - no, that's not good either. -- mailto:av1...@comtv.ru
