Date: Mon, 9 Apr 2018 15:09:42 +0200
Jens Maurer <Jens.Maurer_at_[hidden]> writes:
> The current proposal to support macros in modules does not allow the
> contents of a later import be influenced by macros defined by a former
> import.
You mean the module interface is immutable to macros defined in the
importing translation unit? Yes, allowing this would be pure lunacy.
> It's just that modules can make macros available to importing
> translation units, and will be visible there.
The following will still be possible, right?
#import foo // Exports macro FOO.
#ifdef FOO
# import bar
#endif
Or even this:
#import FOO
This will require the back-and-forth between the build system and the
compiler I mentioned earlier.
> The current proposal to support macros in modules does not allow the
> contents of a later import be influenced by macros defined by a former
> import.
You mean the module interface is immutable to macros defined in the
importing translation unit? Yes, allowing this would be pure lunacy.
> It's just that modules can make macros available to importing
> translation units, and will be visible there.
The following will still be possible, right?
#import foo // Exports macro FOO.
#ifdef FOO
# import bar
#endif
Or even this:
#import FOO
This will require the back-and-forth between the build system and the
compiler I mentioned earlier.
Received on 2018-04-09 15:09:51