I like pragma once, should be standardized, but the problem is in the details of the wording.

I know that the paper acknowledges that some compiler issues a warning if they appear in the source file, and that the paper doesn't advocate for the warning either way. But the note seems to suggest otherwise.
It would be best if the standard had no notion of what a source file is, and you should remove the note that a compiler could issue a warning, let that just be a vendor detail.

The description of how the directive should behave isn't the best, describing in in terms of an ifdef block is not good.


________________________________
From: Std-Proposals <std-proposals-bounces_at_[hidden]> on behalf of Jeremy Rifkin via Std-Proposals <std-proposals_at_[hidden]>
Sent: Tuesday, August 27, 2024 4:01:08 PM
To: Jeremy Rifkin via Std-Proposals <std-proposals_at_[hidden]>
Cc: Jeremy Rifkin <rifkin.jer_at_[hidden]>
Subject: [std-proposals] Revising #pragma once

Hi,
I have drafted a proposal for standardizing #pragma once. This has been previously proposed a few years ago and I recognize that on top of being difficult to standardize, existing opinions on this topic may render the paper dead on arrival. However, due to its widespread nature and concerns about portability contributing to it not being used more I think it's worth revisiting. I have uploaded the first draft at: https://jeremy-rifkin.github.io/cpp-proposals/drafts/pragma-once-draft-1.html.

Cheers,
Jeremy