Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign

CC based semantic highlight

(1/4) > >>

Alpha:
I have begun exploration of full semantic highlighting, provided by the knowledge from CC's parser.  The attached patch is able to show colors, however it is very temperamental.  Also, if you type anything into the editor, it will break.
The colors were chosen at random; suggestions for these would be appreciated.

This code currently uses some operations which are potentially unsafe.  You have been warned.

ollydbg:
Great work. Look at the screen shot, it is so beautiful.
I'm going to test it right now.

ollydbg:
Testing result: sometimes, C::B hangs. :)

mistar:
Have a look also on my plugin ;) shouldn't hang ;)
http://forums.codeblocks.org/index.php/topic,16249.msg120205.html#msg120205

ollydbg:

--- Quote from: mistar on February 20, 2013, 10:12:48 am ---Have a look also on my plugin ;) shouldn't hang ;)
http://forums.codeblocks.org/index.php/topic,16249.msg120205.html#msg120205

--- End quote ---
Both you and Alpha did good job, thanks, will take time to test those.

@Alpha, about the hang, I think the locker(there are many lockers in the CC code), but from my point of view, we should remove mostly of them.

TokenTree are the shared resource, sometimes, the worker thread (Parserthread are adding tokens to it), in the other time, the main GUI thread(like the one you implement the semantic highlight should query the TokenTree). I think they should not happen concurrently. I mean if the parser is working, the TokenTree should not accessed by main thread. Either main GUI thread or worker thread can access the TokenTree.

Navigation

[0] Message Index

[#] Next page