Re: header files & #includes
From: Jeff Schwab (jeffplus_at_comcast.net)
Date: 01/01/04
- Next message: jbruno4000: "Re: Aide pour programme: Le préprocesseur Bazorix"
- Previous message: Mike Wahler: "Re: return in void functions"
- In reply to: header_question: "header files & #includes"
- Next in thread: Martijn Lievaart: "Re: header files & #includes"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 01 Jan 2004 16:21:09 -0500
header_question wrote:
> Is it best to place all #include files in one header file seperate
> from all the other files in a project?
>
> What is the logic that determines the order of the #include files,
In most environments, the headers can be included in any order, and
there is no advantage to including them all in one "master header."
In environments that support pre-compiled headers, there is often a
significant advantage to including headers in the same order within each
translation unit. In this case, the "master header" approach can be
useful. Unless you know that you are using such an environment, don't
bother complicating your file structure.
> does it depend on the order of function calls in main?
No.
- Next message: jbruno4000: "Re: Aide pour programme: Le préprocesseur Bazorix"
- Previous message: Mike Wahler: "Re: return in void functions"
- In reply to: header_question: "header files & #includes"
- Next in thread: Martijn Lievaart: "Re: header files & #includes"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|