On Thu, May 31, 2012 at 09:56:01PM -0400, Cristian Tibirna wrote: > I can understand why these functionalities fail: the symbol resolution is > based on the actual parsing of the full unfolding of the current file. Since > an .icc lacks (and doesn't need) an #include of the corresponding .h file, > this mechanism fails. > > Unfortunately I know very little of the current parsing code (or the llvm- > based alternative for what matters). > > Thus my question: is this a known issue?
Yes. > (in fact, I know it should be, I > reported it in QTCREATORBUG-2309). Does somebody have an idea for the actual > reasons and (mercifully) for eventual solutions? I guess one could check the project for files with #include "your.icc" and if there's exactly one, parse the .icc as if all the preceding parts hat been included in the icc instead. Andre' _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
