C / C++ / MFC

for(int x=0;x<count  && !breakouter;x++)
{
  for(int y=0;y<count;y++)
  {
    breakouter = true;
    break;
  } 
}

Maximilien wrote:

Probably one of the last valid usecase for goto. Especially if more than 2 inner loops.

outermost:     <loop control outermost>
                 <outermost statements>

intermediate:    <loop control intermediate>
                   <intermediate statements>

inner:             <loop control inner>
                     <statements>
                     exit intermediate;
                   <end inner>

                   <more intermediate statements>
                 <end intermediate>

                 <more outermost statements>
                <end outermost>

Salvatore Terress wrote:

is "TEST" defined?

Mircea Neacsu wrote:

Another strategy is to use an “uber include” that includes all or a lot of other h files, but it can slow down compilation.

Mircea Neacsu wrote:

Another strategy is to use an “uber include” that includes all or a lot of other h files, but it can slow down compilation.

Sort of in reverse direction, opposite intelisense way.

Is there?

trønderen wrote:

I could challenge you to create a setup to prove the significance of this: A compilation that would consistently take noticeably (more than 1%) longer compilation time with an "uber include" than with individual includes for what you really need

[k5054@localhost]$ cat ex1.cpp
#include <iostream>

int main()
{
    std::cout << "Hello World\n";
}
[k5054@localhost]$ time g++ ex1.cpp

real    0m0.208s
user    0m0.148s
sys     0m0.058s
[k5054@localhost]$ cat ex2.cpp
#include <bits/stdc++.h>

int main()
{
    std::cout << "Hello World\n";
}
[k5054@localhost]$ time g++ ex2.cpp

real    0m0.865s
user    0m0.718s
sys     0m0.142s
[k5054@localhost]$