[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: [Kde-bindings] Common work for Qt4 bindings
From:       Roberto Raggi <roberto () kdevelop ! org>
Date:       2005-09-13 13:22:30
Message-ID: 200509131522.31565.roberto () kdevelop ! org
[Download RAW message or body]

Hi!

I'm happy you want to use the new KDevelop parser to generate the bindings :-) 
The parser is in good shape, but the symbol table needs a lot of work.

On Tuesday 13 September 2005 13:48, Richard Dale wrote:
> On Tuesday 13 September 2005 14:34, Eric Jardim wrote:
> > 2005/9/13, Richard Dale <Richard_Dale@tipitina.demon.co.uk>:
> > > I would expect so, but I'm not sure if it will have a full
> > > pre-processor.
> >
> > Why not? It would be nice to have introspectable information about
> > signals, slots, properties. Think how this would help KDE development.
> > Think about refactoring, too.
in Qt we define a special macro (Q_MOC_RUN) when moc is running. If Q_MOC_RUN 
is defined then we don't expand the Qt macros (e.g. signals, slots, 
Q_PROPERTY, and so on...). My goal is to make the parser compatible with 
Q_MOC_RUN

> It will be general purpose and not-KDE specific, but different to a parser
> you would have in a complete C++ compiler. For instance, with code
> completion, it must be faster than gcc and only parse incremental changes
> as you edit the source.
exactly :-)

ciao robe

_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]