Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
Intergrate the nativeparser_base to our parsertest project
ollydbg:
--- Quote from: MortenMacFly on July 11, 2012, 12:20:04 pm ---
BTW: I am thinking of a directory structure as attached. It is an archive of the new/moved files without (!) the files that did not change. It incorporates all the work you had provided with cc_patch2. I renamed "parsertest" to "cc_test" and in the end we want to test CC, not only the parser. Have a look at the "tree.txt" file which shows the complete directory structure for reference. As I said: The files missing in the archive are the same as in SVN.
Would that be a good thing to do?
--- End quote ---
Good！ That's fine. Thanks.
BTW: I'm currently testing some new Token kind like "tkClassTemplate", "tkClassTemplate", and "tkClassTemplateSpecialization" which support some kind of better template handling, but there are still a lot of work to do.
ollydbg:
There is a question, I see test.h belong to cc_test.cbp
--- Code: --- <Unit filename="cc_test\test.h">
<Option target="<{~None~}>" />
</Unit>
--- End code ---
This may cause some issue. E.g. When you are testing a parser hang problem, you put some code snippet to test.h, then you open the cc_test.cbp in a C::B , as test.h belong to cbp, the parser in C::B will parse it, this will cause the host C::B hangs.
So, I think we should remove "test.h" from cc_test.cbp to avoid such hang issue.
MortenMacFly:
--- Quote from: ollydbg on July 11, 2012, 03:40:28 pm ---So, I think we should remove "test.h" from cc_test.cbp to avoid such hang issue.
--- End quote ---
It doesn't belong to a project nor a target though. Are you sure that it is being parsed therefore? I thought only files that belong to a project/target are being parsed...?!
EDIT: If you are happy with the layout I would do the same in trunk, but only the changed / moved files, not (yet) the new template stuff. Is that OK?
ollydbg:
--- Quote from: MortenMacFly on July 11, 2012, 05:17:48 pm ---
--- Quote from: ollydbg on July 11, 2012, 03:40:28 pm ---So, I think we should remove "test.h" from cc_test.cbp to avoid such hang issue.
--- End quote ---
It doesn't belong to a project nor a target though. Are you sure that it is being parsed therefore? I thought only files that belong to a project/target are being parsed...?!
--- End quote ---
You may not understand my idea. For test.h which contain some code snippet will let the parser hang. I only want the cc_test.exe(parsertest.exe) to parse it, not the normal C::B. Because if a normal C::B hangs, I have no way to develop/debug the cc_test.exe.
--- Quote ---EDIT: If you are happy with the layout I would do the same in trunk, but only the changed / moved files, not (yet) the new template stuff. Is that OK?
--- End quote ---
OK, please go ahead.
MortenMacFly:
--- Quote from: ollydbg on July 12, 2012, 02:17:04 am ---You may not understand my idea.
--- End quote ---
...maybe I need to rre-phrase. As you see:
--- Code: --- <Unit filename="cc_test\test.h">
<Option target="<{~None~}>" />
</Unit>
--- End code ---
...although the file is in the project, it belongs to a the special target "{~None~}" which means in no target it is checked. I was under the impression hat only those files are parsed, that belong to a real target (like "default") and this file only in case it is being opened (which you don't need to do). How does CC collect its list of files to parse precisely? I'll have a look...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version