David Nolden zwabel at
Sat Feb 9 01:20:22 UTC 2008

On Friday 08 February 2008 23:53:06 Andreas Pakulat wrote:
> Hi,
> so python support is back with a (hopefully) more easily usable AST.
> I have again started to look into DUChain and such things and one thing
> I crossed is this whole ParsingEnvironment stuff. And I'm wondering: How
> do I handle this for Python.
> I mean, I currently don't see any need for having the same file parsed
> in different environment (as opposed to C++ where different macros can
> be active). Should I just stick with KUrl for identifying a file and
> creating HashedString and IdentifiedFile instances from that on the fly
> when the API needs it?

There is a lot that you can simply ignore with languages that don't have a 
preprocessor. The whole ParsingEnvironment stuff is one of them. ;)

You can simply address your files by using IdentifiedFile(fileName, 0) or 
similar, and construct all your HashedString file-names using 
KUrl::prettyUrl() as needed(ond of course also the opposite direction 
wherever necessary).

> Andreas, who'd like to see 2 or 3 people sit down and work over DUChain
> docs and C++ code comments :)

Hackathon is coming ;)

greetings, David

More information about the KDevelop-devel mailing list