On Mon, Sep 2, 2024, at 07:53, Tiago Freire wrote:
>> I have intentionally adjusted made a package with the same file installed to multiple different places. the reason, company politics demanded it. I felt dirty when I did it but I have my job which is less a footgun than something that would get me fired. You say you can solve all situations where this exists but in my case the problem is not technical so you cannot
>
> Which is understandable. I know what you mean. I've been there. That's
> one of the causes of the problem.
> It doesn't work for you, that is fine.
> But as I have stated, you don't have to migrate from include guards to
> anything else.


It isn't just me that cannot it is every other third party that hopes to sell their library to me in the future. If they migrate it is no sale. (patching third party libraries is annoyng enough before the lawyers look at the contract)

> My argument is that not everyone has that problem.
> And thus, not need to be subject to that same pain. It should not break
> your code overnight; standardized or not, you would have to
> intentionally do something for that to be a problem for you.
> This feature already exists, your compiler already can use it. There's
> just no documentation that says it's actually available everywhere
> (despite the fact that it already is), let that sink in for a moment.
>
>
> -----Original Message-----
> From: Henry Miller <hank_at_[hidden]>
> Sent: Monday, September 2, 2024 2:44 PM
> To: Henry Miller via Std-Proposals <std-proposals_at_[hidden]>;
> Jonathan Wakely <cxx_at_[hidden]>
> Cc: Tiago Freire <tmiguelf_at_[hidden]>; Tom Honermann
> <tom_at_[hidden]>
> Subject: Re: [std-proposals] Revising #pragma once
>
>
>
> On Mon, Sep 2, 2024, at 07:36, Tiago Freire via Std-Proposals wrote:
>> Nobody is asking shell access to build farms.
>> What I’m asking is for an example minimum setup, what is it that the
>> compiler sees, and how are things setup to even trigger this problem.
>> You can create a github repo, you can describe it in an email.
>> What exactly happens to cause the same file to be seen twice with
>> different paths. And is this setup reasonable enough that it can not
>> be c.onsidered user
>
> I have intentionally adjusted made a package with the same file
> installed to multiple different places. the reason, company politics
> demanded it. I felt dirty when I did it but I have my job which is less
> a footgun than something that would get me fired. You say you can solve
> all situations where this exists but in my case the problem is not
> technical so you cannot