Author Topic: class browser not working  (Read 5434 times)

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
class browser not working
« on: November 17, 2006, 08:03:42 am »
is there any development in progress which disabled the class browser searching in included files ?

with svn rev 3226 the class browser doesn't browse my project files and include files any more,

the debug log always shows
Parsing stage done (3 total parsed files, 31 tokens in 0 minute(s), 0.16 seconds).

with svn rev 3175 (my last backup) it shows
Parsing stage done (62 total parsed files, 17005 tokens in 0 minute(s), 1.656 seconds).

and all symbols in all files are found and available (e.g. for Find declaration, ... )

thx & brgds,
tiwag



Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: class browser not working
« Reply #1 on: November 17, 2006, 08:29:44 am »
I only noticed recently. Will look into it.
Be patient!
This bug will be fixed soon...

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: class browser not working
« Reply #2 on: November 17, 2006, 09:04:53 am »
Fixed.
Be patient!
This bug will be fixed soon...

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9723
Re: class browser not working
« Reply #3 on: November 17, 2006, 09:21:21 am »
Fixed.
That's the kind of magic that always surprises me (I was looking at the diff). How do you track down such issues that fast? For me it takes ages to find such... :-(
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: class browser not working
« Reply #4 on: November 17, 2006, 09:40:54 am »
That's the kind of magic that always surprises me (I was looking at the diff). How do you track down such issues that fast? For me it takes ages to find such... :-(
With regards, Morten.

Hmm, ok, no magic here :)
Maybe I just know better where to start looking first.

In this particular case, the parser could not locate files outside the project. So first I checked the function that actually locates the #include files. Then I checked the function that fills the include dirs array (this is filled before parsing and is used to search for the #include files) and this led me to the root of the problem.
It's all about knowing where to start looking, really...
Be patient!
This bug will be fixed soon...