Re: Cooperating on .defs API specifications
- From: Xavier Ordoquy <xordoquy wanadoo fr>
- To: Owen Taylor <otaylor redhat com>
- Cc: Andreas Rottmann <a rottmann gmx at>, Murray Cumming <murrayc murrayc com>, GNOME Language Bindings <language-bindings gnome org>, guile-gtk discussions <guile-gtk-general gnu org>, shiro acm org, bigloo-lib-devel lists sourceforge net
- Subject: Re: Cooperating on .defs API specifications
- Date: Tue, 30 Mar 2004 22:32:19 +0200
On Tue, 2004-03-30 at 22:01, Owen Taylor wrote:
> If the .defs files are supposed to describe the GTK+ (etc.) interfaces,
> it really seems strange for me to have them maintained independently
> of GTK+.
That's probably because of historical reasons. However, there may also
be some specific things among languages but those specific parts could
be handled by the language code generator
> Why not have .defs files, and generate the binary info from them? The
> .defs files are already there, and they contain more information than
> the headers do (well, comment parsing might change that, but you could
> create comments from the .defs files :)). Just an idea...
I would be interested to know what are the informations the .defs file
have that the header don't. Maybe a more precise deprecated field, but
out of that ?
] [Thread Prev