SDK 4.2.1 Warning - Local variable "xxxxx" is not used...

This warning appears even if there is an assignment made to the variable in question.

If you believe the warning and simply delete the declaration for the variable, your code will crash at runtime due to the attempt to make an assignment to a variable that doesn't exist.

Is this the definition of the warning that is intended ??

I can see the value in a warning that indicates that the value from a variable is never used, indicating that you actually don't need the variable, but the warning as it currently works seems misleading to me.

Jeff

flocsy🤠 over 2 years ago

It's not hazardous. Maybe a little tweaking of the message though could make it easier to understand that the problem is "variable is only assigned but the value is never read"
- Cancel
- Up 0 Down
- More
- Cancel
Jeff over 2 years ago in reply to _psx_

Agreed... I just used it to clean up some lingering code from having diagnostics in place.

That said, the variables are used in that there's an assignment made to them so I find the warning to be misleading and one has to look to see if the variable is actually being used in any way (an assignment to it) before deleting the declaration, or you get a crash at runtime.

It's a hazardous warning in my opinion.
- Cancel
- Up 0 Down
- More
- Cancel
_psx_ over 2 years ago in reply to Jeff

useful to find unexpected error and when you have to clean up code when you run out of memory :)
- Cancel
- Up 0 Down
- More
- Cancel
Jeff over 2 years ago

Fair enough.... user be ware.
- Cancel
- Up 0 Down
- More
- Cancel
jim_m_58 over 2 years ago in reply to _psx_

Exactly! Assigning a value to a variable, even if you do assigns multiple times will trigger the warning unless that variable is actually used in some way.
- Cancel
- Up 0 Down
- More
- Cancel