C Programming: Preprocessor, include files from macro

Question

If I could find a way to do something similar to this, I could cut out hundreds of lines of code in my application, and dramatically increase maintainability. Anyone have any ideas?

#include <stdio.h>

int main( )
{
  #define include_all_files(root)   \
            #include #root "1.h"    \
            #include #root "2.h"    \
            #include #root "3.h"    \
            #include #root "4.h"

  include_all_files( first_library )
  include_all_files( second_library )
  include_all_files( third_library )

  return 0;
}

EDIT:

I appreciate the responses, my example seems to be causing a misdirection in effort, so here is the problem I am actually trying to solve:

I am implementing a finite state machine. Through naming conventions, I have gotten it to be as simple to add a state as:

  STATE(initial_screen)
    #include "initial_screen.state"
  END_STATE

  STATE(login)
    #include "login.state"
  END_STATE

However, if I could answer the original question, I could refactor this down to something as simple as:

  ADD_STATE(initial_screen)
  ADD_STATE(login)

This is because the file name and the state name, and all the underlying wiring and everything else all follow similar conventions. However, I cannot figure out how to implement the include file based on the token received in a macro.

probably better to edit your first post instead of adding comments to it. — AndersK
– AndersK, Commented Nov 20, 2009 at 3:24
Thank you, Anders, I didn't realize I could do that, I have added the edit. — Joshua Cheek
– Joshua Cheek, Commented Nov 20, 2009 at 3:43

Amber · Accepted Answer · 2009-11-20 02:52:40Z

7

Why not just create a header file that itself #includes all of the other header files for the library? Then for each library you'd just include that library's one meta-header.

answered Nov 20, 2009 at 2:52

Amber

531k89 gold badges643 silver badges558 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Left For Archive · Accepted Answer · 2009-11-20 03:57:04Z

3

Unfortunately, this is beyond the capabilities of the C preprocessor.

Have you considered using something like m4 instead?

answered Nov 20, 2009 at 3:57

Left For Archive

2,6761 gold badge19 silver badges20 bronze badges

2 Comments

Joshua Cheek Over a year ago

Thank you, LnxPrgr3, I'll have to read the docs to see if it is compatible with my school computers, but this is the kind of thing I have been desiring for a while, I think ^^

Joshua Cheek Over a year ago

Lol, it is already installed on my school computers ^_^ Thank you so much :D

caf · Accepted Answer · 2009-11-20 04:02:12Z

2

To solve your clarified problem, you could just refactor initial_screen.state and login.state so that they start with STATE() and end with END_STATE. Then you can just do:

#include "initial_screen.state"
#include "login.state"

...which is equivalent to what you're after - it's just an #include instead of an ADD_STATE.

answered Nov 20, 2009 at 4:02

caf

241k42 gold badges344 silver badges479 bronze badges

Comments

Cory Petosky · Accepted Answer · 2009-11-20 02:53:32Z

1

In file includes.h

#include "1.h"
#include "2.h"
#include "3.h"

In all other files

#include "includes.h"

answered Nov 20, 2009 at 2:53

Cory Petosky

12.7k4 gold badges43 silver badges44 bronze badges

Comments

Community · Accepted Answer · 2017-05-23 12:31:04Z

The #include pre-process directive being itself handled at in the same step as the macro evaluation, this would likely not work. I don't believe the pre-processing can be recursive. (or iterative, for that matter).

Instead, the typical way this is done is to create a small include file which includes all the desired #includes. See Cory Petosky's reponse for an illustration.

A word of caution:
While this may cut hundreds of line of code, you should consider that these are "easy" lines of code. One typically skims over them, unlike lines of codes associated with the true logic of the program.

Furthermore, explicitly listing the individual includes necessary for a given file provide a bit of self documentation, and make it easier for refactoring the code when needed.

Edit: This just in ;-)
Someone just asked this SO question Good idea to put all project headers into one file?, and the responses seem to generally agree with my take that there's typically little gain to be had from grouping headers.

Collectives™ on Stack Overflow

C Programming: Preprocessor, include files from macro

5 Answers 5

Comments

2 Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

Comments

2 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related