User forums > Using Code::Blocks
codecompletion parser stops parsing
MortenMacFly:
--- Quote from: oBFusCATed on November 23, 2012, 08:34:24 am ---Probably the full default.conf should be needed.
--- End quote ---
I think I am able to reproduce meanwhile. I switched to "one parser per WS" and now I see this, too.
However: If your projects use several compilers its not wise to do that. The reason is simple: The parser will ix #includes from different compilers then and the CC you get might be wrong.
So, although we still need to fix this later on, for you (Martin K.) a probably solution is to switch to "one parser per project", which should also be the default option.
Martin K.:
--- Quote from: MortenMacFly on November 23, 2012, 08:47:01 am ---
--- Quote from: oBFusCATed on November 23, 2012, 08:34:24 am ---Probably the full default.conf should be needed.
--- End quote ---
I think I am able to reproduce meanwhile. I switched to "one parser per WS" and now I see this, too.
However: If your projects use several compilers its not wise to do that. The reason is simple: The parser will ix #includes from different compilers then and the CC you get might be wrong.
So, although we still need to fix this later on, for you (Martin K.) a probably solution is to switch to "one parser per project", which should also be the default option.
--- End quote ---
Switching to "one parser per project" toggles another problem: CC parses only the active project or the project wich was double clicked in the projects view. When i expand a not active project in the project s view to show me one source file and open this source file, then (sometimes!) no parsing of this project is triggered and i cannot find any declaration/implementation/... of any object in this opened source file.
Martin
MortenMacFly:
--- Quote from: Martin K. on November 23, 2012, 09:15:05 am ---then (sometimes!) no parsing of this project is triggered and i cannot find any declaration/implementation/... of any object in this opened source file.
--- End quote ---
This "sometimes" worries me a bit ???, but you can adjust the behaviour by simply allowing more parsers.
This settings depends on the workspace/project layout you are used to use. For some people, what you call "project" are targets. Thus, having many of these parsers may not be wise for them. For you, having more projects, but rather small ones with less targets, you can safely increase the number of parsers per project and the issue should be gone.
Martin K.:
--- Quote from: MortenMacFly on November 23, 2012, 09:54:56 am ---
--- Quote from: Martin K. on November 23, 2012, 09:15:05 am ---then (sometimes!) no parsing of this project is triggered and i cannot find any declaration/implementation/... of any object in this opened source file.
--- End quote ---
This "sometimes" worries me a bit ???, but you can adjust the behaviour by simply allowing more parsers.
This settings depends on the workspace/project layout you are used to use. For some people, what you call "project" are targets. Thus, having many of these parsers may not be wise for them. For you, having more projects, but rather small ones with less targets, you can safely increase the number of parsers per project and the issue should be gone.
--- End quote ---
I haven't had a deeper look inside CC but in the "on parser per project" mode it seems to parse a project if:
- the active project changes and this project was not scanned before
- a "double click" on a project node occurs and this project was not scanned before
- any source of a not scanned project opens and this project was not scanned before
but when i have a workspace with more than one project inside and several project are sharing one or more source files, than this "shared" sourcefile triggers the parser process only at the first time it opens. When i select the same source file inside of another - not scanned - project, than this doens't trigger a new parser process.
Is this understandable? I should really work on my english.
Martin
ollydbg:
--- Quote from: Martin K. on November 23, 2012, 10:09:09 am ---I haven't had a deeper look inside CC but in the "on parser per project" mod it seems to parse a project/target if:
- the active target changes and this target was not scanned before
- a "double click" on a target node occurs and this target was not scanned before
- any source of a not scanned target opens and this target was not scanned before
--- End quote ---
I'm confused. look at the image below, and it looks like your "target" means a c::b project? ;)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version