Review Request: Extend KDevPlatform API a bit to allow custom import strategies

[Sven Brauch]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101754/
-----------------------------------------------------------

(Updated June 25, 2011, 12:40 a.m.)


Review request for KDevelop.


Summary (updated)
-------

This adds two small functions to the API which make it possible to manually add contexts to a topContexts importer map. Python language support makes use of this in the following case:

When importing a single declaration from a given top-context -- like required for the following: "from x import foo", which imports the declaration "foo" from the module "x" -- the context a declaration was taken from needs to be tracked, so it will not be auto-cleaned (making the importing context lose alias declarations). Using a function like addImportedParentContext() would do this automatically, but for obvious reasons those functions do not work in this case (because only a single declaration should be imported, not a whole context).


Diffs
-----

  language/duchain/topducontext.h 6198a8f 
  language/duchain/topducontext.cpp 402bd34 

Diff: http://git.reviewboard.kde.org/r/101754/diff


Testing
-------

Seems to work in my case, and should not break anything as it just adds two small functions, not touching existing functionality.


Thanks,

Sven

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110625/8b892370/attachment.html>