User forums > Using Code::Blocks
Conditional Code :: Blocks. highlighting in the editor
ollydbg:
--- Quote from: yvesdm3000 on December 12, 2015, 02:32:33 pm ---Mmh, I guess I'll have to do the same thing in Clang CC ;-)
It will get to be weird once we start using compiler-specific macro's as it should actually use the ones from the compiler and not Clang unless Clang is also the compiler...
Yves
--- End quote ---
I think clang can do better than the one I have made in my previous post.
If I remember correctly, there is a plugin called semantic highlight, which uses libclang, see here: Semantic highlight. I think it does not feed the macro definitions to scintilla, instead, it use its own c++ lexer to highlight the editor.
ollydbg:
--- Quote from: SmallTed on December 12, 2015, 10:07:01 am ---OllyDbg after what you wrote, I can probably off because I have no such knowledge about these tools.
Will the new version of CodeBlocks improve this problem?
--- End quote ---
I think we don't have enough time to make such feature in the new release.
As you know, we will release a 15.12 release.
SmallTed:
ollydbg
--- Quote ---I think we don't have enough time to make such feature in the new release.
As you know, we will release a 15.12 release.
--- End quote ---
It will be add to new release 15.22.
It would be a summary of your job.
Maybe one or two days later but this function is useful,
especially when the project is large and you're tired.
SmallTed
ollydbg:
--- Quote from: SmallTed on December 12, 2015, 04:40:53 pm ---ollydbg
--- Quote ---I think we don't have enough time to make such feature in the new release.
As you know, we will release a 15.12 release.
--- End quote ---
It will be add to new release 15.22.
It would be a summary of your job.
Maybe one or two days later but this function is useful,
especially when the project is large and you're tired.
SmallTed
--- End quote ---
15.12 means 2015, December. So, there is no 15.22.
You may try a nightly build version of you need such feature(after the feature is committed to trunk)
MortenMacFly:
--- Quote from: ollydbg on December 12, 2015, 01:23:12 pm ---Guys, I have implement this feature. It works quite well(but as you know, it does not work 100% correctly) as I tested.
--- End quote ---
As usual, changes in scintilla should either be reported upstream to scintilla or (worst solution) be highlighted as C::B changes.
Is the change really needed? (Why?) Can't this be set from outside?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version