MSDN documentation error? “If the procedure is Shared, all its local variables are automatically shared. This includes the Static variables.”

Question

I was reviewing the MSDN documentation on VB.Net\'s little-used Static keyword for local variables. My question is not about how Static works (I personally plan

Answer 1

That particular piece of documentation is wrong. Local variables declared in a Shared method are no different than locals declared in a non-Shared method. The only behavior difference for locals comes into play with they are declared with the Static modifier.

I'll alert the appropriate team about it.

EDIT

The team in charge of the documentation was alerted and will be correcting the documentation in the very near future.

Answer 2

No, it's talking nonsense. It continues being utterly broken in the next paragraph:

If the procedure is not Shared, its local variables are instance variables.

Local variables aren't instance variables...

Whoever wrote that page appears not to understand local variables at all. Goodness knows what they'd make of recursion. Mind you, it starts off reasonably:

Normally, a local variable in a procedure ceases to exist as soon as the procedure stops.

... but that statement is clearly in contradiction to the later ones. Sigh.

I suggest you file a bug on Connect.