Today I investigated a logical bug in our software and figured out that this is related to the way VB.NET thread variables inside a loop.
Let\'s say I have the follo
If you think this may be a problem with your codebase or your programmers, in your coding style specify that all uninitialised variables are declared at the start of the routine. This had been a common style guideline (especially for VB) until the prevalence of type inference.
Of course it doesn't avoid the problem, just makes it more obvious.