> The standardisation would need to describe the actual system calls needed to achieve identification.

Would it?
Maybe the problem is to try to define it in these terms.
The way I see it, you don't have to.
Even though same path= same file seems to be bare minimum, do we need to specify that we are reading a file from a filesystem? Do we want to even put on such constraints? Just say generic "same thing" and call it a day.
Honestly, what else do you need to say?


________________________________
From: Std-Proposals <std-proposals-bounces_at_[hidden]> on behalf of Thiago Macieira via Std-Proposals <std-proposals_at_[hidden]>
Sent: Sunday, September 1, 2024 5:34:01 PM
To: std-proposals_at_[hidden] <std-proposals_at_[hidden]>
Cc: Thiago Macieira <thiago_at_[hidden]>
Subject: Re: [std-proposals] Revising #pragma once

On Sunday 1 September 2024 00:56:52 GMT-7 Mike Reed via Std-Proposals wrote:
> Of course one could argue that you went through all that pain *because*
> there isn't a standard on #once. If there were then everyone would
> implement it the same, devs would use it knowing exactly what to expect and
> you wouldn't have gone through all that pain.
> The problem is, is it possible to produce such a spec? Does the current
> proposal succeed where the previous proposal failed?

The standardisation would need to describe the actual system calls needed to
achieve identification. Is this something the standard wants to get into?
Probably not.

--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Principal Engineer - Intel DCAI Platform & System Engineering
--
Std-Proposals mailing list
Std-Proposals_at_[hidden]
https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals