Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
CC based semantic highlight
MortenMacFly:
--- Quote from: oBFusCATed on March 30, 2013, 07:49:32 pm ---@other devs: please state your opinion here, I won't revert if for a couple of days.
--- End quote ---
Well I like and in fact use it although I realise its not working 100%. Maybe this should be turned off by default and an explanation in the settings points out that this is not meant to work perfectly.
oBFusCATed:
--- Quote from: MortenMacFly on March 31, 2013, 05:23:50 pm ---Well I like and in fact use it although I realise its not working 100%. Maybe this should be turned off by default and an explanation in the settings points out that this is not meant to work perfectly.
--- End quote ---
For sure it should be turned off by default if it stays.
But the problem is that this is a half feature - broken and hard to extend.
The thing is that the semantic part of the name of the feature implies that it uses the CC and so it should work 100% of the time (ignoring CC parser bugs).
But this is not the case. And we have a prototype (I've not looked at it, so I cannot tell how good it is) that does better job.
Also this feature is almost the same as the broken highlight for stl stuff, but the brokenness is a bit more hidden.
I know that implementing this properly is hard, because of the need to modify scintilla, but I'm sure it is doable.
Also the semantic highlight should not be part of the CC plugin! It should be part of the SDK or it should be separated in a plugin.
Alpha:
It is off by default now. If you would like to revert it completely, go ahead, however from previous discussions of this patch, it sounded as though there are at least several people who do find it useful in its current (flawed) state.
--- Quote from: oBFusCATed on March 31, 2013, 05:49:01 pm ---Also the semantic highlight should not be part of the CC plugin! It should be part of the SDK or it should be separated in a plugin.
--- End quote ---
Agreed, but do we yet have a way for a seperate plugin to access the data in CC's parser?
oBFusCATed:
--- Quote from: Alpha on April 04, 2013, 12:58:07 am ---It is off by default now. If you would like to revert it completely, go ahead, however from previous discussions of this patch, it sounded as though there are at least several
people who do find it useful in its current (flawed) state.
--- End quote ---
OK, but what do you do when they ask you to highlight the member functions differently and then the local variables?
--- Quote from: Alpha on April 04, 2013, 12:58:07 am ---Agreed, but do we yet have a way for a seperate plugin to access the data in CC's parser?
--- End quote ---
Nope, but we should start from somewhere otherwise we will never have it.
BTW: The current implementation is quite laggy and thus quite annoying. Something happens but I don't know when.
p.s. Anyone else from the devs which wants to express opinion. Currently we are 1:1.
MortenMacFly:
--- Quote from: oBFusCATed on April 04, 2013, 08:19:06 am ---p.s. Anyone else from the devs which wants to express opinion. Currently we are 1:1.
--- End quote ---
Express opinion on what exactly?
For semantic highlight and access to CC internals my preferences are to use clang, maybe through Eran's engine. I think we can never be better than that - its amazing how fast the code base and functional support grows. So having a nice abstraction layer for clang will serve way more than providing interfaces to access (our) CC internals IMHO...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version