Scope rules

[n2xssvv g02gfr12930]

Although I rarely if ever have a problem with scope, I was wondering
whether anybody knows of good reference, (book, web page, etc), that
covers scope rules. Hopefully this will be helpful to others.

JB

 

[Victor Bazarov]

Although I rarely if ever have a problem with scope, I was wondering
whether anybody knows of good reference, (book, web page, etc), that
covers scope rules. Hopefully this will be helpful to others.

You mean like "Always keep the scope of the name as tight as possible"?
Or do you mean like "overloading only relates to functions in the same
scope" and the related "derived class scope is tighter than the base
class scope (and included in it)"?

V

 

[Frederick Gotham]

n2xssvv g02gfr12930 posted:

Although I rarely if ever have a problem with scope, I was wondering
whether anybody knows of good reference, (book, web page, etc), that
covers scope rules. Hopefully this will be helpful to others.

A rule of thumb would be:

An object exists from the point of its definition, until the next
closing brace. (Unless it's static of course).


If you define an object within a "for" loop as follows:

for(int i; {}


Then its scope is as if you wrote:

{
int i;

for(; {}

}

 

[n2xssvv g02gfr12930]

You mean like "Always keep the scope of the name as tight as possible"?
Or do you mean like "overloading only relates to functions in the same
scope" and the related "derived class scope is tighter than the base
class scope (and included in it)"?

V

All of those points would be nice, with examples demonstrating the how
and the why. Perhaps I should create some web pages on scope covering
class, namespace, code scope, and any others you'd like to suggest.
Thanks for your response, and no doubt you could think of countless
examples.

JB