Date: Fri, 30 May 2025 15:49:08 +0100
On Friday, May 30, 2025, Sebastian Wittmeier via Std-Proposals wrote:
>
> Another topic is about interface ownership. Even if the internal Microsoft
> memory format can be reverse-engineered and would currently work in a
> stable way, you codify it into an international standard. That is not nice,
> you are taking away Microsoft's ownership over their ABI.
>
The best thing would be just to ask Microsoft to add this feature to their
"cl.exe" program. It wouldn't be a one-way road -- Microsoft executables
would also be able to link successfully with GNU g++ DLL's, or Embarcadero
DLL's. If we got everyone on board with it then it would make sense to
standardise it with classes and functions like std::abi and std::abi_wrap.
I've emailed guys in Microsoft before but I never get a reply, not even
that Raymond Chen guy who has a decent blog.
>
> Another topic is about interface ownership. Even if the internal Microsoft
> memory format can be reverse-engineered and would currently work in a
> stable way, you codify it into an international standard. That is not nice,
> you are taking away Microsoft's ownership over their ABI.
>
The best thing would be just to ask Microsoft to add this feature to their
"cl.exe" program. It wouldn't be a one-way road -- Microsoft executables
would also be able to link successfully with GNU g++ DLL's, or Embarcadero
DLL's. If we got everyone on board with it then it would make sense to
standardise it with classes and functions like std::abi and std::abi_wrap.
I've emailed guys in Microsoft before but I never get a reply, not even
that Raymond Chen guy who has a decent blog.
Received on 2025-05-30 14:49:11