From: Nitro <ni...@dr...> - 2006-09-02 12:58:32
|
Am 02.09.2006, 02:36 Uhr, schrieb John Lenz <le...@cs...>: > On 09/01/06 18:29, Nitro wrote: >> A similar way that I use to rename classes and functions is to parse >> everything with swig -xml and then run an xml parser on this to extra= ct >> the necessary symbols. You could use this to generate the proper = >> #defines >> into another file. >> My script is basically a customized version of this one here (credits= to >> Robin Dunn from wxPython): >> http://cvs.wxwidgets.org/viewcvs.cgi/*checkout*/wxWidgets/wxPython/co= nfig.py?rev=3D1.71.2.19&content-type=3Dtext/plain >> . Just search for "processXML" (at the very bottom) in there to get t= he >> function which extracts the proper xml data. >> >> -Matthias > > > Since a bunch of people ask about this feature, it might be nice to ad= d > that script in as an example in the Example directory. Then people ca= n > copy it from SWIG and customize it themselves. > > If anyone wants to make a simple example, of using a script to rename > variables, I will gladly add it to CVS. > > John A shortcut to using this script is to use %rename with the regular = expression things. I've never tried that way though. In bigger projects = = the xml building + parsing step takes up a considerable amount of time, = so = the %rename way might be preferred in that case for simple operations. Afaik GCC also provides some xml mode, so for people using only GCC they= = might investigate this method, too. At the moment I don't have enough time at hands to provide a complete = example, I also don't know how to write makefiles. I could provide a = python xml parser script though which is customized for the example alon= g = with an example interface file. |