| T O P I C R E V I E W |
| Uniwares |
Posted - Mar 15 2022 : 12:45:18 PM
For some reason, the "aux" var gets colored wrongly in this context. C#, Win7, VS2017.
|
| 4 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Mar 18 2022 : 12:36:11 PM
I have a pattern. If you enter:
bool parsed;
on the line above, so "parsed" isn't being declared on the same line, "aux" should now be understood correctly as a new variable being declared.
case=147955 |
| feline |
Posted - Mar 18 2022 : 09:56:42 AM
With code based on yours, rather than my simple example to prove the syntax works, I am seeing the same problem. But in my simple "prove the syntax" example the variable is coloured correctly, both when passed in and used...
Trying to make sense of this now. |
| Uniwares |
Posted - Mar 18 2022 : 08:11:59 AM
VA doesnt show anything on the definition field, but goes to the declaration, tooltip shows correct information. VA definitely IS confused here, subsequent uses of the variable continue to be colored wrongly.
|
| feline |
Posted - Mar 18 2022 : 07:45:14 AM
Just checking I understand correctly, "aux" is being declared on the first line. This is what I am testing here, and not seeing any problems with the colouring of the variable declared inside the function call.
If you place the caret into "aux" on either line are you getting the correct information in VA's context and definition fields?
What about Alt-G on aux on the second line, where it is used? I am trying to tell if this is a colouring only problem, or if VA is really confused here. |
|
|
