Review Request 118238: Get the top-level context associated with a QML module

[Denis Steckelmacher]

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

(Updated May 22, 2014, 2:56 p.m.)


Review request for KDevelop.


Changes
-------

Complete version of the support for import statements (but without the plugin.qmltypes files, because it would have made the diff nearly 1MB big). If "import QtQuick 1.0" is added to a QML file used in the testsuite, the corresponding test crashes. This is the latest code that I use for testing.


Repository: kdev-qmljs


Description
-------

This patch adds a method that returns the top-level DUContext associated with a QML plugin. It uses KStandardDirs to get the plugin.qmltypes file associated with the module (these files are installed by the plugin in KDE_DATA/kdevqmljssupport/qmlplugins/Module.qml), and then schedules a parse job for the file. If the file has already been parsed, then its top level context is returned. This method will be used to implement import statements. The module files and the complete support for import statements can be found in the "import_statements" of kde:scratch/dsteckelmacher.


Diffs (updated)
-----

  duchain/declarationbuilder.h 265d0ce 
  duchain/declarationbuilder.cpp 10701bd 
  duchain/parsesession.h 0facef4 
  duchain/parsesession.cpp 998e5b0 

Diff: https://git.reviewboard.kde.org/r/118238/diff/


Testing
-------

This patch cannot be tested as the method is not yet called, but the support for import statements is already implemented in my kde:scratch/dsteckelmacher repository. Import statements work right in KDevelop, but the unit tests segfault when they have to parse a file containing an import. The crash always happens in an openDeclaration() or currentDeclaration() call, and if I comment the faulting call, another one will crash. The crash does not happen anymore if I remove the calls to "bgparser->addDocument" added in this patch, and does not happen in a complete KDevelop instance.

I'm therefore wondering how the background parser can interact with openDeclaration(). I've checked and a DUChainReadLock or a DUChainWriteLock is always held when openDeclaration() is called, but maybe there are other locks that may be needed. I turn to more advanced KDevelop developers on this matter.


Thanks,

Denis Steckelmacher

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20140522/10b8ae07/attachment.html>