Some asm help for the 'thiscall' calling convention?

[Adam Sansier via Digitalmars-d-learn]

On Thursday, 14 July 2016 at 14:01:29 UTC, Kagamin wrote:
> On Wednesday, 13 July 2016 at 22:30:51 UTC, Adam Sansier wrote:
>> Um, no, I revived it so that people searching for answers 
>> wouldn't be led astray by idiots who pretend to know 
>> everything.
>
> My word is not COM specification of course, there's the 
> official documentation and tons of books about COM, what one 
> prefers, they all say the same thing, one doesn't need to trust 
> me on that. This one is a particularly good read: 
> https://www.amazon.com/Inside-Microsoft-Programming-Dale-Rogerson/dp/1572313498/ explains all fundamentals of COM.

That isn't the point. The point is you make absolute claims that 
are obviously not true. It is a personality deficiency you have, 
not about trust.

It's like if you claim all prime numbers are odd, state it as 
absolute fact, then when someone says "Hey, I found a prime 
number that is even" you automatically assume they must be wrong. 
Instead of looking at it as objectively. All it does is lead to 
confusion.

Unless you know something to be absolute fact, don't state it as 
such then don't pretend it to be such... Your still doing that by 
trying to show "proof" that you are right.

Yet you are wrong. Regardless what the asio standard does right 
or wrong, it uses COM, correct? Is asio not well established? Yes 
it is. Hence it proves that not all COM is as you think it is. 
Just accept it, learn that there are no absolutes and that you 
can be wrong, and the world would be a better place.