Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 Error parsing .cpp file

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
pocruadhlaoich Posted - Apr 15 2009 : 08:00:13 AM
Hi,
my boss is currently evaluating Visual Assist to bring it to our company but he has run into a problem with one particular file. The .h will parse correctly but the .cpp won't, it only seems to parse a fraction of it. This is using VAX build 1715.

Below are the log files generated:
4   L A T E S T    R E P L I E S    (Newest First)
feline Posted - Apr 16 2009 : 4:53:54 PM
These invisible characters might have also upset the compiler, unless it treated them as white space and stripped them out.

I have no idea how they got into your code, but I am glad you found them and removed them. Turning on show whitespace (CTRL-SHIFT-8 by default) might have shown them up in the editor.

Hopefully you won't have this problem again, and that VA works well for you.
pocruadhlaoich Posted - Apr 16 2009 : 09:37:56 AM
Hi,
the problem is now resolved. The list of methods in the file was only partial previously. It appears that somehow there was some invisible character that had crept into the code after a merge. Deleting this symbol meant that VA was able to parse the whole file again. We found the problem by working out function by function where VA was able to parse and where it couldn't. Looking at the .cpp file in a hex editor, VA failed to parse this:
0x0D, 0x0A, 0x00, 0x0D, 0x0A, 0x09, 0x09
Does this mean anything to you? This was as far as I could take it...
If you do know the reason for what happened, I would be very interested to hear it. Thanks!
feline Posted - Apr 15 2009 : 12:40:32 PM
If you open the Alt-m (list of methods in file) list does this show all of the functions in this problem file, or does it only show some functions?

If you show VA Outline how much of this file does it show?

It sounds like there is something part way down the cpp file that is confusing our parser. Unmatched brackets have been known to cause this problem, e.g. code like this:

void functionCausingProblems
{
#if 0
    {
        {
            {
#endif
}


If the alt-m list or VA Outline give you a clue as to where the problem starts, can you look at the code and see if there is anything "odd" that might explain the problem?
pocruadhlaoich Posted - Apr 15 2009 : 08:19:55 AM
The files were too large to post here, so I have made them available from this location:

ftp://visualassistbug.inspecvision.com/httpsdocs/vaxbug

username = visualassist
password = vaxbug

VAssist.log
va.log

Thanks,
Patrick

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000