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

ParserTester for codecompletion plugin

<< < (5/6) > >>

MortenMacFly:

--- Quote from: ollydbg on February 25, 2010, 07:45:02 am ---By the way, Loaden suggests that we could have different replacement string set for different compiler. :D

--- End quote ---
I wouldn't do that by the compiler. The reasons are:

1.) CC needs to "talk" to the compiler which may not be present. CC should also work without the compiler (the compiler is another plugin in the end).
2.) You can use e.g. Visual C++ SDK's with GCC just fine (like Direct/X for example). So the replacements do in fact not depend on the compiler as you see.

Better proposal: Try to "identify" commonly used SDK's (like base SDK's) upon typical identifiers in the header files For example: If you encounter _GLIBCXX_STD switch to the right set of replacements tokens and re-parse. If you encounter _STD_BEGIN switch (or better append) this set.

Notice that you can also use GCC / VC libraries / header files mixed. So a combination os replacements tokens may make sense.

ollydbg:

--- Quote from: MortenMacFly on February 26, 2010, 06:07:49 pm ---Notice that you can also use GCC / VC libraries / header files mixed. So a combination os replacements tokens may make sense.

--- End quote ---
Ok, in this situation, both replacement string for GCC and VC should be used.

ollydbg:
Here is a improved parserTester version 2.
A lot of GUI improved by Loaden. Added a "find" non-model dialog.
Also, we have moved the project sources to a separate folder instead of the "/plugins/codecompletion/parser"

So, you need to download the 7z package, and unzip it. it should have a "ptest" folder, you need to paste this folder (include all the files) to "codecompletion/parser", so, now, all the source files were in "codecompletion/parser/ptest".

Also, a you need to apply these patches to let the "parserTester" project compile successfully. ( This patch never hurt the building of standard CC)

In this patch, I have fix this problem: Insert all class method without implementation question

Comments are welcome!!!

By the way, I don't change these code snippet in tokenizer.cpp ,but the TortoiseSVN always thought I was changing that...

--- Code: ---#ifdef __WXMSW__ // This is a Windows only bug!
    else if (c == 178 || c == 179 || c == 185) // fetch ² and ³
    {
        str = c;
        MoveToNextChar();
    }
#endif


--- End code ---

I'm not sure why.






[attachment deleted by admin]

Loaden:
Sorry, my fault, in "ParserTesterV2.7z" compressed package, the "mainfdsfef.cpp" is unnecessary, and could be deleted.

Loaden:
Refactoring code, and add two methods: PrintTree and PrintList.
It should work better.

[attachment deleted by admin]

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version