Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
Check macro usage on every identifier like token: issues and discussions
Huki:
Hi, I'm back...
--- Quote from: ollydbg on June 19, 2015, 04:23:23 pm ---Hi, Morten, this is a reply after two months... How time flies. :(
I think not much people are testing my patch serials. I'm considering what is the time to let those patches into our SVN repo. I don't have a clean plan, maybe, we can let them in, and we may have more testers through nightly build versions. ;) What's your or other guy's idea?
--- End quote ---
So far it has been very stable for me. I just checked out the latest revision and found these patches have already made into master.. that's good. :) I found only one regression, due to commit r10230, but this is not related to your cc_macro patches.
Well, I tried to follow Morten's earlier advice. I have now forked Obfuscated's github repo. All my commits are available here, in branch "huki". On the top you can see 3 new bugfixes against the latest master. Now, do you want me to continue posting them in the forum as patches, or should I issue a pull request? (I can create a new branch with those 3 commits.)
ollydbg:
Hi, huki, thanks, and I will clone your branch, and see/test your three commits.
Huki:
I have added test cases for my fixes (this commit).
ollydbg:
--- Quote from: Huki on October 26, 2015, 07:54:15 pm ---I have added test cases for my fixes (this commit).
--- End quote ---
Thanks, but I think the file "cc_loop_variables.cpp" currently doesn't work under our cctest framework, since the cctest can only test codecompletion in the global scope. In our normal CodeCompletion plugin, we have some other methods to retrieve the scope information.
ollydbg:
I see other works on your github branch, which use CC to support the preprocessor of Scintilla's gray out of inactive conditional preprocessor branch. I don't know the details, but it looks like you are explicitly load a dll(shared library) from the sdk or src. My idea is that currently, the SDK.dll is a bridge, and all plugin should implement the interface, I have some simple diagram added days ago in the wiki, see Plugin structure of C::B - CodeBlocks.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version