Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 1645: strange parsing errors
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

.oisyn
Tomato Guru

162 Posts

Posted - Jul 27 2008 :  6:45:52 PM  Show Profile  Reply with Quote
I'm getting this very weird error where parsing gets all ****ed up when I try to define a certain constructor of a nested class that has a certain type as parameter. As soon as the type of this parameter is longer than 6 characters, parsing goes all weird. Using a type less than 6 characters, or defining the ctor as a function rather than a ctor, all is fine.

I can't reproduce this in an isolated test-setup, and even when copying the whole contents of that particular file to another one the bug doesn't show up in that other file.

Using a type with only 6 characters (or less)


Making that type 1 character longer


It works for any random sequence of characters.

This information isn't probably of much use to you guys but I thought you should know anyway

Edited by - .oisyn on Jul 27 2008 6:59:27 PM

feline
Whole Tomato Software

United Kingdom
18947 Posts

Posted - Jul 28 2008 :  09:29:53 AM  Show Profile  Reply with Quote
When this goes wrong, are you able to simplify the code and still see the problem? I suspect you could delete the "next()" member function, and the two operator overloads as well, and still see the problem.

I am wondering how simple you can make the code and still see the problem.

Since this is solution specific I am guessing there is some form of clash / conflict with something else in your solution. The simpler you can make the problem code, the fewer the points of conflict, so this should make it easier to find the conflict. At least in theory.

zen is the art of being at one with the two'ness
Go to Top of Page

.oisyn
Tomato Guru

162 Posts

Posted - Jul 28 2008 :  8:49:05 PM  Show Profile  Reply with Quote
After re-opening the solution the problem went away. VA X seems to have been confused somehow. I can't really reproduce it in any way.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18947 Posts

Posted - Jul 29 2008 :  11:25:37 AM  Show Profile  Reply with Quote
*sigh* it is good that the problem has gone away. Hopefully you will not have any more problems like this, since problems you cannot reproduce are hard to study.

zen is the art of being at one with the two'ness
Go to Top of Page

.oisyn
Tomato Guru

162 Posts

Posted - Aug 04 2008 :  06:27:59 AM  Show Profile  Reply with Quote
Is there any way I can provide you with useful data whenever this happens again? A copy of the symbol database for instance? Or a minidump?
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18947 Posts

Posted - Aug 04 2008 :  09:20:03 AM  Show Profile  Reply with Quote
Log files might help:

http://docs.wholetomato.com?W305

A copy of VA's symbol database might also help.

zen is the art of being at one with the two'ness
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000