Re: Thoughts on mm-common and gmmproc

[Murray Cumming <murrayc murrayc com>]

On Wed, 2010-01-06 at 19:00 +0100, Krzesimir Nowak wrote:
> - I was wondering if current defs file format is all that great. Why
> not
> use XML for example? True, it can get quite lengthy, but there are
> lots
> of software parsing this stuff and format is rather quite reliable -
> unpaired parentheses and usage of double quotes in property docs
> aren't
> going to screw anything and <, >, & could be replaced with &smth;
> entities.
> 
> - Generating defs file is the horror story. For signals defs - compile
> and run a little program, for enums defs - run an enum.pl script, for
> methods defs - h2def.py, for xml docs - docextract_to_xml.py, for
> vfuncs
> defs - just write them by hand. Le gasp! Also, some of these tools are
> not perfect or fine-tuned for mm-modules needs - pygobject's
> docextract_to_xml.py does not extract enum documentation, h2def.py
> hickups on functions with a pointer to function as their parameter
> (some
> g_test function has them). I'd rather avoid writing Another Defs or
> XML
> Generating Tool to have enum docs. But frankly speaking this is sort
> of
> hard to resolve with one tool at first glance. Also, I recently tried
> to
> regenerate all defs for atkmm, gdkmm and gtkmm and in the end I got
> some
> cryptic error about end of file while wrapping GtkSettings, so
> updating
> defs is also painful. 

We hope to use the new .gir files, which should actually be correct and
widely shared:
http://live.gnome.org/GObjectIntrospection

However, I hope any gmmproc rewrite does the .defs/.gir switch as a
separate task. 

-- 
murrayc murrayc com
www.murrayc.com
www.openismus.com