Date: Sat, 31 May 2025 22:29:55 -0400
On Sat, May 31, 2025 at 7:46 PM Frederick Virchanza Gotham via
Std-Proposals <std-proposals_at_[hidden]> wrote:
>
>
>
> On Friday, May 30, 2025, Oliver Hunt wrote:
>>
>>
>>
>> That said, the real core issue here is that the vtable layout is platform ABI, and the actual fix is for non-msvc compilers to generate code that conforms to the platform ABI.
>
>
>
>
> I've been saying for a while now that C++ is held back by Microsoft's implementation of polymorphism; I posted the following here 6 months ago:
>
> https://lists.isocpp.org/std-proposals/2024/11/11541.php
Um, maybe you didn't realize that the person you are responding to is
saying the exact opposite. That is, "non-msvc" compilers should do
what MSVC says to do. The platform ABI (aka: what Windows says) is not
the problem; the problem is compilers that don't conform to it (ie:
not MSVC).
Oh, and it is definitely a choice to bring up a statement that you
famously provided no evidence for as evidence for the opposite of what
you want.
Std-Proposals <std-proposals_at_[hidden]> wrote:
>
>
>
> On Friday, May 30, 2025, Oliver Hunt wrote:
>>
>>
>>
>> That said, the real core issue here is that the vtable layout is platform ABI, and the actual fix is for non-msvc compilers to generate code that conforms to the platform ABI.
>
>
>
>
> I've been saying for a while now that C++ is held back by Microsoft's implementation of polymorphism; I posted the following here 6 months ago:
>
> https://lists.isocpp.org/std-proposals/2024/11/11541.php
Um, maybe you didn't realize that the person you are responding to is
saying the exact opposite. That is, "non-msvc" compilers should do
what MSVC says to do. The platform ABI (aka: what Windows says) is not
the problem; the problem is compilers that don't conform to it (ie:
not MSVC).
Oh, and it is definitely a choice to bring up a statement that you
famously provided no evidence for as evidence for the opposite of what
you want.
Received on 2025-06-01 02:30:12