Skip to content

Conversation

@AlisdairM
Copy link
Contributor

[module.global.frag] is entirely part of phase 7 of translation, and it makes no sense to talk of preprocessing directive in the grammar term declaration-seq. Strike the note rather than try to turn it into something meaningful.

jensmaurer
jensmaurer previously approved these changes Nov 3, 2025
Copy link
Member

@jensmaurer jensmaurer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm ok with that, in particular there is an adjacent pull request that adds a bit of clarification to [cpp.pre].

@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.

@jensmaurer jensmaurer self-requested a review November 4, 2025 14:25
@jensmaurer jensmaurer dismissed their stale review November 4, 2025 14:26

I changed my mind.

@eisenwave eisenwave added the P3-Other Triaged issue not in P1 or P2 label Nov 5, 2025
[module.global.frag] is entirely part of phase 7 of translation,
and it makes no sense to talk of preprocessing directive in the
grammar term *declaration-seq*.  Strike the note rather than try
to turn it into something meaningful.
@AlisdairM AlisdairM force-pushed the meaningless_pp_note_in_global_frag branch from 2d87ef2 to e0a9d13 Compare November 12, 2025 22:50
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