ChatGPT解决这个技术问题 Extra ChatGPT

For loop inside its own curly braces

I have come across this for-loop layout:

#include <iostream>
int main()
{
    {
        for (int i = 0; i != 10; ++i)
        {
            std::cout << "delete i->second;" << std::endl;
        }
    }

    {
        for (size_t i = 0; i < 20; ++i)
        {
            std::cout << "delete m_indices[i];" << std::endl;
        }
    }
    return 0;
}

I was wondering what this extra layer of braces is for? This appears a few times in our code base.

They're completely superfluous in the code snippet you posted
what compilers have been used with this code? Specifically did VS 6 get used?
@EdNorman now with your edit it is much clearer. It seems that the correct answer is the one provided by UKMonkey. With modern C++ compiler you can simple drop the curly braces.
Alternatively, it could be generated code (sighed someone just coming to grips with Rhapsody)
One possible reason is if the code once had (or is intended to have in future) OpenMP parallel directives.

J
Jaden Travnik

Once upon a time, many moons ago, VS6 existed and was popular. It failed however to conform to a number of C++ standards; which was reasonable at the time as it was released just before (on the same year) the standard was officially released; it did however adhere to the draft of the standard as far as I'm aware.

One of the standards that changed between the draft and the official standard, was the lifetime of for loop variables created in the first section; leading to the following code failing to compile

{
    for (int i=0; i<1; ++i){}
    for (int i=0; i<2; ++i){}
}

because i was redefined by the second for loop.

While other compilers also suffered this bug; I highlight the VS6 one because it remained the only version of visual studio for a number of years after the release of the standard, but never released an update for this particular issue; meaning that it had a more significant impact.

A solution to this is to force the whole for loop into its own scope as you have shown.


No need to find VS6 to see that @bolov, set "Force Conformance in For Loop Scope" to "No" in VS2015, and enjoy ;-)
@alain "option 'Zc:forScope-' has been deprecated and will be removed in a future release" and compiles without a problem... I am sad
GCC prior to version 2.7 also exhibited this behaviour. See docs.freebsd.org/info/g++FAQ/g++FAQ.info.for_scope.html
@Damon it wasn't when VS6 was first released; however when the standards changed, an update that conformed to them was never released. VS6 remained in popular for a good few years after the standards were changed.
Attributing this to a sin of an old Microsoft compiler is bogus. This behaviour was actually a feature of draft C++ standards, and a number of compilers did this (not only Microsoft compilers). From memory, it was changed in a draft during about 1995 to make the variable local to the loop - about three years before the first C++ standard was ratified. So most C++ compilers predating (about) 1996 worked this way.
p
pensono

{ and } will create a scope and if you define some variables in the scope you cannot access them from outside. But for already create that scope. So

{for(int i = 0; i < count; ++i){}} 

is the same as

for(int i = 0; i < count; ++i){}

but if you define something between them, there is a difference

{int a = 0; for(int i = 0; i < count; ++i){}}

In this example, a won't be accessible from outside scope.


b
bolov

In your particular example there is no reason for them.

Sometimes you could want to create a scope for a variable:

float average;
// ...

{
int sum = 0;
for (int i = 0; i < count; ++i)
{
   sum += v[i];
}
average = (float)sum / count;
}

// use average
// sum not in scope here

However I see this an anti-pattern. Usually if you find yourself in need of doing this then most likely the for should be its own function.


Okay if you think it should be in its own function (I can think of many times where that would only add overhead at the very least but I'm not going to go there) a hypothetical question for you: what about if you need a specific local scope to a switch case? There certainly are times that adding an additional scope (which of course a function does too) (note that for your example I don[t at all think a separate function is a bad idea) is unnecessary but other times it's not that simple even if there are other ways.
R
Ron

It's a block scope marked by {} braces. It is usually used to mark the area of automatic storage. In your case it doesn't seem to do anything as the for loop has its own scope in standard C++.