[Kde-bindings] New parser branch (Was: Dumping the source DOM?)

[Richard Dale]

On Thursday 14 July 2005 09:12, Marcus wrote:
> Yes, I'm using gccxml for my bindings and to build a "database" of the API.
> I do not know where or when Roberto Raggi posted the original message. I
> only see the partial message in stratified quotes from Richard here.
Yes, I cc'd my comments about a suggestion for using the gccxml translation 
unit dump as some sort of parser for KDevelop, because the discussion on 
kdevelop-devel sounded very similar to ones we've had on this list. 

There seem to be pros and cons of using a translation unit dump as opposed to 
parsing the headers. Then whether xml/xpath should be used for runtime 
introspection or just for generating the bindings in the first place and 
doing runtime introspection based on either extending the moc, or having 
something similar to a more complete moc like Smoke v1.

KDevelop 4 will have a refactoring engine where rules can be specified to 
operate on an AST to specify text transformations. Generating language 
bindings is like an extreme form of refactoring, so to me the subjects seem 
related.

-- Richard

> On Wednesday 13 July 2005 6:36 am, Richard Dale wrote:
> > On Wednesday 13 July 2005 13:55, Roberto Raggi wrote:
> > > On Wednesday 13 July 2005 13:43, Sylvain Joyeux wrote:
> > > > Do you think it would be possible, though, to use gcc-xml (or
> > > > whatever "static" parser) to parse external dependencies and build
> > > > persistent datastores ? It would workaround the problems you have to
> > > > parse C++ in real-time (which is far from being simple) when advanced
> > > > functionalities are not needed.
>
> _______________________________________________
> Kde-bindings mailing list
> Kde-bindings at kde.org
> https://mail.kde.org/mailman/listinfo/kde-bindings