Thread: Defining functions below int main() - Best practices?

I don't understand why one would define some functions below int main()...???

What is the point of that exactly?

It would seem to me that the best practice would be to have int main() at the bottom of all code. Why would you write code beneath the main() function?

Also, in a book entitled "Practical C++" by Robert W. McGregor, in example code, the main() function always has the return type void instead of int. Why is this? I thought the main function always has to be int? Or does it just depend on the compiler/platform?

Some people consider it to be clearer. Program control flow starts at main, and logically people like to read downward. It's not that big of a deal either way.

As for main, old, pre-standard compilers, programs and books often used void instead of int. It's not a big deal, either, but the standard states that it should be int so that the calling programs can expect a non-random return value. If your book uses void main, it might be worth considering a more modern or better book, but if you continue to use it just switch to int for main.

I don't know...
I just find it easier to have main() at the bottom of the code, seeing as you if you choose to define functions below the main() function, you still have to declare them above it, so what's the point?

Originally Posted by brewbuck

That means you're choosing where to place functions in relation to other functions because you don't want to write prototypes. The functions should be listed in some kind of logical order, not whatever order happens to be compilable.

No, correction: I'm still writing prototypes of functions (which, as I understand it, has to be done), just I have both the prototypes and the definitions above int main, because it makes it easier to read that way.

Originally Posted by laserlight

More accurately, because you find it easier to read that way. As Daved pointed out, some people find it easier to read with the definition of the global main function at the top. Do what you will, but follow the rules if a project that you are working on mandates it.

Affirmative. At least we can agree there.
If I was on a multiple-programmer project, and I wasn't the one who started and was running the project, I would indeed follow whatever rules the Head Honcho defined.

Here is the deal.

main() must return an int for obvious reasons already explained.

As far as functions being below main(), is, as explained, governed by project coding rules or up to the lead developer. Whats your technique then? There really is no wrong way, but more of how readable is your code and helps to strengthen self documentation.

If you provide function declarations, then the function definitions can be below main().

- By providing function declaration before main(), provides more of an OOP approach of which you can move those function declarations to another header file for easier manageability/code modifications latter.

- Also as the project grows in size or if more than 2 programmers need to compile in changes, then moving your functions to another header file, again, adds to the OOPness of the project.

- If everything must be at the top of main(), then your declares and definitions must be provided as this helps the compiler.(Thats my understanding)

Originally Posted by slingerland3g

Here is the deal.

main() must return an int for obvious reasons already explained.

As far as functions being below main(), is, as explained, governed by project coding rules or up to the lead developer. Whats your technique then? There really is no wrong way, but more of how readable is your code and helps to strengthen self documentation.

If you provide function declarations, then the function definitions can be below main().

- By providing function declaration before main(), provides more of an OOP approach of which you can move those function declarations to another header file for easier manageability/code modifications latter.

- Also as the project grows in size or if more than 2 programmers need to compile in changes, then moving your functions to another header file, again, adds to the OOPness of the project.

- If everything must be at the top of main(), then your declares and definitions must be provided as this helps the compiler.(Thats my understanding)

True, you provide some good points. The truth is, I had not thought about putting all functions other than main() in header file(s) until it was suggested in this thread, and so it seemed to me the best way to do it would be to put both declarations and definitions above int main. But, yeah, I can easily see how putting all function declarations (I'm assuming you can't put the definitions in too?) in header files, with the definitions below int main() would improve the readability of the whole code.

Originally Posted by laserlight

Personally, I feel that "modular" and "modularity" should be used instead of "OOP" and "OOPness" in this context. I do not see anything particularly object oriented about moving forward declarations to a header file.

True, yet from time to time in analyzing code I do see separate header files for just declarations only, the modularity of such an implementation of header file madness I am not sure on.