Thread: int main() question

It only has to exist
Where you put it in your code doesn't matter

> but what is its purpose
To basically say "start here"

>> so why then some programs have the int main at the end.
The actual order of the source file is irrelevant, the compiler takes care of putting things into their correct places in the executable.

> means int main runs b4 any other function correct?
Correct

> so why then some programs have the int main at the end. the code b4 it what does it do?
Style
The position of a function has nothing to do with when it gets executed

Code:

void foo ( ) { }
void bar ( ) { }
int main ( ) {
  bar();
  foo();
  return 0;
}

Reorder it however you want, doesn't make a difference.

Put foo() in foo.c and bar() in bar.c (this is typical of large programs spanning hundreds, possibly thousands of source files). Only one of them has main(), and it appears just once.

> they have to wait for int main to start?
You're thinking in terms of some ancient interpreted language like BASIC

>>Main will be the starting point for the entire program
An exception to the rule?:

Code:

 #include <iostream>
 
 class myClass
 {
   public:
     myClass()
     {
       std::cout <<"Class being created!" <<std::endl;
     }
 };
 
 myClass c1;
 
 int main(void)
 {
   std::cout <<"main being run!" <<std::endl;
 }
 
 /*
 
 Output:
 
 Class being created!
 main being run!
 
 */

Here the object is created and it's constructor is invoked as part of the process. As its global, it gets created before main gets to run.

So in summary, objects with file scope are created first, and their constructors are called, and after all the constructors have returned, then int main() is the next thing to run.