I have blame the parser.cpp, and find that the macro usage like:
#ifndef STANDALONE
#include <configmanager.h>
#include <logmanager.h>
#include <editormanager.h>
#include <manager.h>
#include <globals.h>
#include <infowindow.h>
#endif // STANDALONE
In the parser.cpp is came from the "revision 5" when the parser.cpp was initially added to the trunk.
So, my question is: what does these preprocessor directive used for ?
It seems when we defined this macro, I still can't build a stand alone program. (The same effort is the parserTest project were have created in this ParserTester for codecompletion plugin (http://forums.codeblocks.org/index.php/topic,12066.0.html)
In the ParserTester project, we only include the "parserthread" class, so the Parser.cpp is not included.
So, my suggestion is: Can these preprocessor directive removed? I can't find any reason we should keep it there.
Thanks.
Maybe, the boss mandrav can ask this question. :D Thanks.
At that point, it was possible to compile the CC plugin files (with an additional main.cpp file) as a standalone executable for easier testing of the parser.
I doubt this can be done nowadays so feel free to ignore it or even remove it.
Thanks for your reply!!!
I doubt this can be done nowadays
Ha, the parserTest project can just do this.