| T O P I C R E V I E W |
| reltham |
Posted - Jul 20 2006 : 02:03:57 AM
In class function definitions if my code looks like this:
int MyClass :: MyMethod(int Var)
{
...
}
Then the parser will not think the method is part of the class and all members of MyClass with be underlined in red and treated as undefined.
If I just removed the spaces around the :: and wait a few seconds then it will be fine and the red underlines will go away and it will treat them as defined.
This occured in 1528 also, I didn't go back further. |
| 8 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Sep 19 2006 : 01:53:06 AM
Fixed in 1535. |
| support |
Posted - Sep 05 2006 : 3:58:20 PM
We bumped priority. |
| reltham |
Posted - Sep 05 2006 : 3:47:01 PM
There's been a few new builds since I brought this issue up, and it's still not fixed (just checked 1534).
Is this even on the radar? |
| reltham |
Posted - Aug 09 2006 : 3:43:22 PM
More clarification:
int MyClass :: MyFunc() // fails
int MyClass ::MyFunc() // fails
int MyClass:: MyFunc() // works
int MyClass::MyFunc() // works
By fails I mean that meber vars in the body of the functions are underlined red and VAX thinks they are invalid (no alt-g or anything).
MS intellisense seems to works fine in any case.
This is still an issue with build 1531 (as expected). |
| jpizzi |
Posted - Jul 28 2006 : 02:25:17 AM
No word, yet. It looks like it is still in the queue to have someone look at, so I wouldn't expect it in the next build. There has not been a release since you reported this. |
| reltham |
Posted - Jul 27 2006 : 2:15:44 PM
Any word on this one yet? It would be nice if a fix for this was in the next build. |
| reltham |
Posted - Jul 20 2006 : 1:53:20 PM
I HATE the spaces there, but it's pre-existing code that I'm not really allowed to go change freely. |
| jpizzi |
Posted - Jul 20 2006 : 02:23:54 AM
Why would anyone want to put spaces there? 
case=1740 |
