Skip to content

Conversation

@AlisdairM
Copy link
Contributor

Add a note confirming that executing preprocessor directives within the pp-global-module-fragment can produce text-lines.

Add a note confirming that executing preprocessor directives
within the pp-global-module-fragment can produce text-lines.
@AlisdairM AlisdairM changed the title [cpp.pre] Add note on preprocessing directives in *pp-global-module-fragment* [cpp.pre] Add note on preprocessing directives in pp-global-module-fragment Nov 3, 2025
@tkoeppe
Copy link
Contributor

tkoeppe commented Nov 4, 2025

@jensmaurer Did I get that right that you'd only want #8389 if we also merge this PR?

@jensmaurer
Copy link
Member

I've thought about this some more. I think the preprocessor treatment of the global module fragment is so surprisingly different from any other context that I would want to retain a cross-reference from phase 7 [module.global.frag] to [cpp.pre] in some form. This is a comment about #8389.

And that would decouple those two pull requests.

@jensmaurer jensmaurer removed their assignment Nov 4, 2025
@eisenwave eisenwave added the P3-Other Triaged issue not in P1 or P2 label Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P3-Other Triaged issue not in P1 or P2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants