Well, that's really unfortunate, because it makes CB uncompetitive with VC, at least in this area. Both code samples do work correctly in VC 2010, and it seems not to use the 'include entire namespace hack' you suggest. That means that the problem is soluble, and I think it is an important one. I recommend CB very strongly in all my posts and blogging about C, but if a major language feature like this is not supported, I may have to tone this down:-( Well, at least CB's FOSS competitor CodeLite doesn't seem to get it right either. The basics works fine.But when I started trying playing with it responded very slow on large files with many include filesThe key was to implement the caching for clang using an automated mechanism of PCH creation by stripping the include files from a source file and generate a dummy header file which will be used as our PCH file.
![Codelite Autocomplete Not Working Codelite Autocomplete Not Working](http://codelite.org/images/codelite-7.1/status-bar-menu-2.png)
Codelite Setup with Pictures An extended guide on how to setup Codelite for SOMA scripting, this time with pictures and known issues at the bottom. Feel free to add to this guide as long as it is fitting.
The generated PCH is then 'injected' to the command line by the -include switch.Another thing to put it mind is to implement a mechanism that will invalidate the cache (some entries) when needed (e.g. New header file was added to the source file)If you need assist, please free to email me or start a new thread about it.Eran. Which reminds me, Eran:We had in mind to 'join forces' by trying to attach the CC codecompletion (stand-alone) library into Code::Blocks. I once tried and I have a few stubs available, but I simply don't have the time and meanwhile I'm afraid the interface to CodeLite's CC and C::B's CC has changed.So - if anybody is willing to write a CC wrapper for Code::Blocks based on Eran's work - step forward. I think Eran did nice job concerning the separation of concerns, so it can really be seen as a stand-alone framework where we just need to match C::B's CC interface to the one of Erans.However, as long as there is no measurement/guess about the effort our own CC has higher priority.
In the end for my (and probably only my) purposes it works really well, in fact I rarely miss any information/feature. The basics works fine.But when I started trying playing with it responded very slow on large files with many include filesThe key was to implement the caching for clang using an automated mechanism of PCH creation by stripping the include files from a source file and generate a dummy header file which will be used as our PCH file. The generated PCH is then 'injected' to the command line by the -include switch.Another thing to put it mind is to implement a mechanism that will invalidate the cache (some entries) when needed (e.g.
New header file was added to the source file)If you need assist, please free to email me or start a new thread about it.Eran.