Date: Sun, 01 Sep 2024 08:33:52 -0700
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.
> 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
Received on 2024-09-01 15:33:56