[cairo] Re: Munging header files for export (and other) attributes
cworth at cworth.org
Tue Aug 30 09:30:13 PDT 2005
On Tue, 30 Aug 2005 12:40:08 +0200, Doodle wrote:
> I wouldn't like to be a troll but I don't see why a header file has to
> be so much readable.
We already do quite a bit of work to keep these public header files
readable, such as aligning the parameter lists. Some people do read
header files, so decreasing the readability here will impact them.
I would just like to avoid doing that if possible.
> Well, thinking more in this way, one should say that writing the
> 'void' in front of function prototypes that return no value is
> a pure noise,
No, because some functions have a void return type while others do
not. So there is information in the word "void". It's tagging
functions as "public" in an installed public header file that only
contains public functions that doesn't add any information.
> Unfortunately this assumes that every platform has sed installed.
If there are platforms for which the availability of sed is a problem,
the solution could be implemented in a way to do all of its munging
before a tar file is generated, and never in a Makefile.
> meanwhile here is the cairo.h file used on OS/2 (modified by a .c code),
> and the cairo-features.h file which is generated by the OpenWatcom
Thanks. That confirms that the munging we're talking about here would
be perfectly sufficient for what you need, (in terms of generating the
necessary result in cairo.h).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/cairo/attachments/20050830/2d3e3840/attachment.pgp
More information about the cairo