News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Conditional Code :: Blocks. highlighting in the editor

Started by SmallTed, December 11, 2015, 11:46:18 AM

Previous topic - Next topic

ollydbg

Quote from: MortenMacFly on December 13, 2015, 07:11:39 AM
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.
As usual, changes in scintilla should either be reported upstream to scintilla or (worst solution) be highlighted as C::B changes.
OK, I know this, and I won't commit the changes soon, because it need more testing.

Quote
Is the change really needed? (Why?) Can't this be set from outside?
I see that scintilla use either space or "\n" or "\r" as the default delimiter. So, unless we pass all the macro definition without any space in its replacement, we should use "\n" only delimiter. I don't see there is an option outside, you can look at the code snippet I posted in previous posts.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

SmallTed

I downloaded but probably not of this repository.
After compilation code blocks I see svn 10621. you're working on git.
You do not have time now, so I will not bother you.
Quote
15.12 means 2015, December. So, there is no 15.22.
So I was concerned about 15.12, my mistake.
But I see that this is not the version 15.12, maybe later.
SmallTed

ollydbg

If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.