using preprocessed files ?
neundorf at kde.org
Tue Jul 11 19:48:52 UTC 2006
On Tuesday 11 July 2006 20:36, you wrote:
> Hi Alex,
> On Wednesday 12 July 2006 03:40, Alexander Neundorf wrote:
> > would it help us (kdevelop) for things like code completion, code
> > navigation, etc, if the parser etc. could work on the preprocessed files
> > ? Suddenly it would be completely clear where from which header a class
> > comes from, or which members a struct has, since this can all be found in
> > the preprocessed file.
> > If you think this would help us, I'll try to add something to cmake to
> > make it trivial to generate them.
> KDevelop's parser already has internal support for preprocessing. Because
> we want to offer incremental parsing (so that hopefully processing can be
> done real-time, or as close to it as possible), we really need to have this
> control ourselves.
> One thing which will be crucial to code completion etc. is the information
> that cmake uses to invoke gcc, eg. include directories, command line
> defines (-Dblah=foo), etc.
Yes, that's kindof the same idea, but AFAIK until now we don't have this yet.
(but for getting this information no cmake API is required, cmake can simply
Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de
Home: neundorf AT kde.org - http://www.kde.org
alex AT neundorf.net - http://www.neundorf.net
More information about the KDevelop-devel