Recent Posts

Pages: 1 [2] 3 4 ... 10
11
64 Bit Assembler / Re: 64 bit macro glossary
« Last post by aw27 on Today at 12:13:01 AM »
What you are stuck with is the need for a disassembler, debugger
One day they will figure that out by themselves.  :t
12
UASM Assembler Development / Re: UASM 2.46 Release
« Last post by jj2007 on December 11, 2017, 10:59:23 PM »
The pointer syntax (->) can only be used with...

It's very unfortunate that the authors of MASM used the <> as a reserved word; same for the exclamation mark. OTOH, there was not so much choice: {any better?} ^or this^ %no good% ┬žadvocates need these┬ž @mail@ ...
13
The Orphanage / Re: Could have been worse
« Last post by Magnum on December 11, 2017, 10:36:49 PM »
Going to hand dr. today.

Will see if staples can be removed.

14
The Orphanage / Re: Could have been worse
« Last post by Jokaste on December 11, 2017, 10:28:52 PM »
I hope it's not too serious and you're getting better.
 :icon_redface:
15
The Orphanage / Re: Could have been worse
« Last post by Magnum on December 11, 2017, 09:40:51 PM »
Thanks
16
UASM Assembler Development / Re: UASM 2.46 Release
« Last post by johnsa on December 11, 2017, 08:37:41 PM »
On another note, the _V, _INVOKE and other macros that are built-in deal entirely with the OO features. COM having the extra indirection required slightly different handling so internally uses _VCOMINVOKE and _VCOM.

Assuming you don't wanted nested calls, then using _VCOMINVOKE or _INVOKE(for normal OO) is pretty straightforward as per the example in the manual and samples folder.
17
UASM Assembler Development / Re: UASM 2.46 Release
« Last post by johnsa on December 11, 2017, 08:24:33 PM »
Hi,

I'll test out this example and see what the issue is with that line, I suspect it may be to do with using the OFFSET operator in the macro.

The pointer syntax (->) can only be used with OINTERFACE, CLASS and COMINTERFACE (internally these types are tracked as being different from regular structures and different from each other).

In the case of the ointerface or class the vtable exists inside the instance itself, where-as with com the object contains a pointer to the vtable. So the keep the syntax consistent it handles them differently by adding extra indirection in the case of COM. Using the ointerface or class with -> requires use of a vtable (OPTION VTABLE:ON) where-as for performance reasons if you have a class that you know is not going to be dynamically modified, and hence no reason to go via a vtable, with that off the call removes the extra indirection and goes straight to the method call.

I'll get back to you asap with a fix for the offset issue.

18
The Orphanage / Re: Could have been worse
« Last post by caballero on December 11, 2017, 07:33:50 PM »
The good news is you are right :t That's the important
19
WINDOWS.INC Project / Re: Ca'nt find the Winsock2 libs and includes
« Last post by rsala on December 11, 2017, 07:13:27 PM »
 :t
20
WINDOWS.INC Project / Re: Ca'nt find the Winsock2 libs and includes
« Last post by Raistlin on December 11, 2017, 06:36:08 PM »
Thanks Ramon - will check it out !  :t
Pages: 1 [2] 3 4 ... 10