Author Topic: what's wrong with the C++ parser?  (Read 4607 times)

Andrey

  • Guest
what's wrong with the C++ parser?
« on: November 20, 2009, 06:02:37 pm »
firstly, let me thank you for the C::B, it's cool!

From time to time I run into problems with auto-completion (C::B 8.02, ubuntu 9.10 i686) for symbols for the parsed files (I can tell that because some other symbols from the same <path>/*.h appear as expected).

Here is an example:
I've added /usr/include/X11 to project's C++ parser options and after reopening the project completion understands XGenericEvent from Xlib.h, but doesn't understand XEvent from the same file. Actually it doesn't understand any of XGetXXX functions.

Another similar problem is that after a method is added to superclass (in my case it was done by wxFormBuilder), and files were reloaded by C::B, "insert > class method..." dialog doesn't recognize the new method neither in that class, not in its descendants.

Also, it would be great if parser could be invoked manually, by a toolbar button/menu, in order not to close*open the project. I would like C::B to give more feedback on parser status - what was parsed, what wasn't, etc (maybe some diagnosis?)


Thanks.
« Last Edit: November 20, 2009, 06:09:28 pm by Andrey »

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9723
Re: what's wrong with the C++ parser?
« Reply #1 on: November 20, 2009, 10:03:49 pm »
Also, it would be great if parser could be invoked manually, by a toolbar button/menu, in order not to close*open the project. I would like C::B to give more feedback on parser status - what was parsed, what wasn't, etc (maybe some diagnosis?)
Concerning the parser you *definitely* want to try a nightly. It has improved a lot and some improvements are still pending which will be applied soon.

About the feedback:
CC has a debugging mode accessible through the symbols browser. You can read all about it in the WiKi here:
http://wiki.codeblocks.org/index.php?title=Code_Completion_Design#Code_completion_debugging_support
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 blueshake

  • Regular
  • ***
  • Posts: 458
Re: what's wrong with the C++ parser?
« Reply #2 on: November 21, 2009, 02:19:51 am »
Quote
some improvements are still pending which will be applied soon.

Just be curious what are they? :wink:
Keep low and hear the sadness of little dog.
I fall in love with a girl,but I don't dare to tell her.What should I do?

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9723
Re: what's wrong with the C++ parser?
« Reply #3 on: November 21, 2009, 08:05:57 pm »
Just be curious what are they? :wink:
You should know when following the forum threads. Some are documentation, cosmetic, some are about template handling. The latter is still kind of untested that's why I don't commit so far.
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