Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
Clang CC
yvesdm3000:
--- Quote from: l_inc on December 08, 2015, 11:11:07 pm ---
--- Quote ---I remind you this is only a prerelease and by all means not a final product, although I do use it for my daily main job now.
--- End quote ---
I understand that. I was just shocked to see the commented private replaced with public and the private methods being used outside of the class scope. This made me scared about the project becoming a heap of crutches even before the first release would come out.
--- End quote ---
Thanks for pointing this out. I've put it back to private. This was most certainly only a debugging measure.
Yves
yvesdm3000:
The mysterious crashes can be removed from the list for my part. I haven't had a 'mysterious' crash anymore for over a month now... There might still be in the Windows-port but I can't do any user-testing with it using my daily job...
Yves
yvesdm3000:
For the C++11 requirement please ask the C::B developers. They seem to be open to include this plugin into mainstream so I don't want to bother them with restricting requirements from my part... And even for myself, I need to compile this thing in RHEL5/CentOS5 although I do think I can manage with C++11.
Yves
l_inc:
yvesdm3000
--- Quote ---For me the plugin does not work with a single TU, it switches TU when the associated document is opened.
--- End quote ---
I was talking about the diagnostics. I've just debugged it a little. And the problem seems to be the GetCurrentTranslationUnitId method, cause it always returns 0. So only the TU that happened to have gotten the m_TranslUnitId == 0 has the diagnostics displayed, which is ensured at the beginning of OnDiagnostics . I removed the if ( m_TranslUnitId == -1 ) condition to always resolve the current TU in GetCurrentTranslationUnitId, and it works OK now.
yvesdm3000:
--- Quote from: l_inc on December 09, 2015, 02:38:49 am ---yvesdm3000
--- Quote ---For me the plugin does not work with a single TU, it switches TU when the associated document is opened.
--- End quote ---
I was talking about the diagnostics. I've just debugged it a little. And the problem seems to be the GetCurrentTranslationUnitId method, cause it always returns 0. So only the TU that happened to have gotten the m_TranslUnitId == 0 has the diagnostics displayed, which is ensured at the beginning of OnDiagnostics . I removed the if ( m_TranslUnitId == -1 ) condition to always resolve the current TU in GetCurrentTranslationUnitId, and it works OK now.
--- End quote ---
You seem to have found a bug there. Thanks for sharing !
Yves
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version