Implementation of the COM interface FileOpenDialog

[Villuy]

just a some stupid ideology as I have seen.
No C for someone is best example?

I not understanded your remark. Just like previous one.

[NoCforMe]

I can at least partially answer that.

All this is clear. But why we are discussing compiler VC++ problems here?

I think the answer to that should be obvious:
It's because the OP chose to code a function (actually an "interface", IFileOpenDialog()) that uses a COM interface.
The COM interface stuff is really only documented (by Micro$oft and others) in C++/C form. Therefore it had to be "translated" from C++/C to assembly language.

And it turns out that doing things this way is less problematic than coding it in the native C++/C. Who would've guessed that?

[TimoVJL]

Component Object Model

Unlike C++, COM provides a stable application binary interface (ABI) that is unaffected by compiler differences.[3] This makes using COM advantageous for object-oriented C++ libraries that are to be used by clients compiled via different compilers.

[satpro]

A COM structure???  I would have.  C'mon.  As would someone with enough knowledge to write the GoAsm assembler in the first place.

NoC, respectfully (if it is possible), take a breath.  Please.  It is glaringly obvious that assembly language is something you "dabble" in, but otherwise don't know jack about.  And, that's being nice.  We are treated to one misguided, angry opinion after another, on every topic -- it's truly maddening at times.

I'm just asking for a little detente, that's all.  It seems like every last topic is railroaded directly into the ground, and in this case you're trying to make an ACTUAL assembler author jump through hoops over a COM structure you know nothing about.  Why?  Who thinks that's right?

I don't.  And I don't do it to you.  Neither does anyone else.  How else can I make the point?  It needs to stop, and only one guy needs to figure out how.  In other words, be nice or go away.  Enough is enough.  This is 2025.  Smarter, more kind.  All the time.  Or bust.

[NoCforMe]

Sorry, not sorry.
Going to ignore your "advice".

[satpro]

Okay.

[Villuy]

I think the answer to that should be obvious:

Unlike C++, COM provides a stable application binary interface (ABI) that is unaffected by compiler differences. This makes using COM advantageous for object-oriented C++ libraries that are to be used by clients compiled via different compilers.

Interfaces are drug addict's thing in WinAPI. So probably yes.