On Fri, 30 Aug 2024 at 02:24, Jeremy Rifkin <rifkin.jer_at_[hidden]> wrote:
> The point of a standard is to provide clear guidelines about what it
> means. If for example, the standard guarantees that symbolic links and
> hard links are handled, then the user can be confident their #pragma
> once code will do what they want unless 1. there could be multiple
> unique copies of the header or 2. they have a setup like Gasper's with
> multiple mount points. In such a case, they should use traditional
> include guards. Libraries in general should use traditional include
> guards, for example.

Right. Any by not standardizing this misfeature, we can explain to
users that it shouldn't
be used anywhere, as it's non-standard for good reasons. Which is the
status quo for
quite many of us.