Does anyone have a simple definition of VARIANT in both 32 and 64-bit?
It doesn't seem to be in the .inc files.
Does this help...
https://masm32.com/board/index.php?topic=2845.msg29946#msg29946 (https://masm32.com/board/index.php?topic=2845.msg29946#msg29946)?
I simply used an obscure forum function called 'search'. :tongue:
Admittedly, not sure if this is what you are looking for...
Quote from: zedd151 on June 28, 2024, 10:44:40 AMI simply used an obscure forum function called 'search'. :tongue:
How droll :biggrin:
I have some code I wrote a long time ago but it includes fields like
.dw2,
.dw1,
.wReserved2,
.vtDifferent to the one you linked to
VARIANT STRUCT
dw1 dd 0CCh
dw2 dd 0CCh
dw3 dd 0CCh
dw4 dd 0CCh
VARIANT ENDSMSDN is its usual helpful self :badgrin:
typedef struct tagVARIANT {
union {
struct {
VARTYPE vt;
WORD wReserved1;
WORD wReserved2;
WORD wReserved3;
union {
LONGLONG llVal;
LONG lVal;
BYTE bVal;
SHORT iVal;
FLOAT fltVal;
DOUBLE dblVal;
VARIANT_BOOL boolVal;
VARIANT_BOOL __OBSOLETE__VARIANT_BOOL;
SCODE scode;
CY cyVal;
DATE date;
BSTR bstrVal;
IUnknown *punkVal;
IDispatch *pdispVal;
SAFEARRAY *parray;
BYTE *pbVal;
SHORT *piVal;
LONG *plVal;
LONGLONG *pllVal;
FLOAT *pfltVal;
DOUBLE *pdblVal;
VARIANT_BOOL *pboolVal;
VARIANT_BOOL *__OBSOLETE__VARIANT_PBOOL;
SCODE *pscode;
CY *pcyVal;
DATE *pdate;
BSTR *pbstrVal;
IUnknown **ppunkVal;
IDispatch **ppdispVal;
SAFEARRAY **pparray;
VARIANT *pvarVal;
PVOID byref;
CHAR cVal;
USHORT uiVal;
ULONG ulVal;
ULONGLONG ullVal;
INT intVal;
UINT uintVal;
DECIMAL *pdecVal;
CHAR *pcVal;
USHORT *puiVal;
ULONG *pulVal;
ULONGLONG *pullVal;
INT *pintVal;
UINT *puintVal;
struct {
PVOID pvRecord;
IRecordInfo *pRecInfo;
} __VARIANT_NAME_4;
} __VARIANT_NAME_3;
} __VARIANT_NAME_2;
DECIMAL decVal;
} __VARIANT_NAME_1;
} VARIANT;
Yikes!
Where is that structure used?
Quote from: NoCforMe on June 28, 2024, 11:07:53 AMYikes!
Where is that structure used?
In a lot of COM interface
shit stuff.
Quote from: sinsi on June 28, 2024, 11:13:16 AMQuote from: NoCforMe on June 28, 2024, 11:07:53 AMYikes!
Where is that structure used?
In a lot of COM interface shit stuff.
Better you than me. :joking:
If I saw that a function would need that structure, I'd pass on it. I prefer simpler code projects.
For anyone else puzzled by what, exactly, COM is, see this new topic I posted (https://masm32.com/board/index.php?topic=12071.0).
Quote from: zedd151 on June 28, 2024, 12:33:54 PMQuote from: sinsi on June 28, 2024, 11:13:16 AMQuote from: NoCforMe on June 28, 2024, 11:07:53 AMYikes!
Where is that structure used?
In a lot of COM interface shit stuff.
Better you than me. :joking:
If I saw that a function would need that structure, I'd pass on it. I prefer simpler code projects.
It looks scary but it's actually quite easy :biggrin:
Quote from: sinsi on June 28, 2024, 10:40:44 AMDoes anyone have a simple definition of VARIANT in both 32 and 64-bit?
MasmBasic.inc:
VARTYPE typedef word
VARIANT struct 16
vt VARTYPE ? ; VARTYPE: wtypes.h says unsigned word
wReserved1 dw ?
wReserved2 dw ?
wReserved3 dw ?
UNION
bstrVal dd ?
pintVal dd ?
parray dd ?
scode dd ?
pvRecord dd ? ; add whatever you need - see oaidl.h
llVal dq ?
lVal dd ?
iVal dw ?
bVal db ?
fltVal REAL4 ?
dblVal REAL8 ?
ends
VARIANT endsCOM is easy, if the methods are well documented. It's a horrible mess (https://masm32.com/board/index.php?msg=126182) if C++ and C# can't agree about the number of arguments to be passed etc.
So we have 4 words then a variable-length member, depending on what vt says?
I used this Variant structure in my type library browser. Bifogar exe och iTypeLib.inc.
VARIANT struct dword ;size 10h
vt word ? ; VT_EMPTY
wReserved1 word ? ;0
wReserved2 word ? ;0
wReserved3 word ? ;0
Union
lVal sdword ? ; VT_I4 A 4-byte integer value is stored in lVal.
bVal byte ? ; VT_UI1 An unsigned 1-byte character is stored in bVal.
iVal sword ? ; VT_I2 A 2-byte integer value is stored in iVal.
fltVal real4 ? ; VT_R4 An IEEE 4-byte real value is stored in fltVal.
dblVal real8 ? ; VT_R8 An 8-byte IEEE real value is stored in dblVal.
boolVal word ? ; VT_BOOL
scode dword ? ; VT_ERROR
cyVal qword ? ; VT_CY A currency value was specified. A currency number is stored as 64-bit (8-byte), two's complement integer, scaled by 10,000 to give a fixed-point number with 15 digits to the left of the decimal point and 4 digits to the right. The value is in cyVal.
date qword ? ; VT_DATE A value denoting a date and time was specified. Dates are represented as double-precision numbers, where midnight, January 1, 1900 is 2.0, January 2, 1900 is 3.0, and so on. The value is passed in date.
;This is the same numbering system used by most
;spreadsheet programs, although some specify
;incorrectly that February 29, 1900 existed, and
;thus set January 1, 1900 to 1.0. The date can be
;converted to and from an MS-DOS representation
;using VariantTimeToDosDateTime, which is discussed
;in Conversion and Manipulation Functions.
bstrVal dword ? ; VT_BSTR A string was passed; it is stored in bstrVal. This pointer must be obtained and freed by the BSTR functions, which are described in Conversion and Manipulation Functions.
punkVal dword ? ; VT_UNKNOWN A pointer to an object that implements the IUnknown interface is passed in punkVal.
pdispVal dword ? ; VT_DISPATCH A pointer to an object was specified. The pointer is in pdispVal. This object is known only to implement IDispatch. The object can be queried as to whether it supports any other desired interface by calling QueryInterface on the object. Objects that do not implement IDispatch should be passed using VT_UNKNOWN.
parray dword ? ; VT_ARRAY For VT_ARRAY | any type, the rule is analogous to the rule for VT_BSTR. All arrays in variants must be allocated with SafeArrayCreate. When releasing or changing the type of a variant with the VT_ARRAY flag set, SafeArrayDestroy is called.
pbVal dword ? ; VT_BYREF+VT_UI1 For VT_BYREF | any type, the memory pointed to by the variant is owned and freed by the caller of the function.
piVal dword ? ; VT_BYREF+VT_I2
plVal dword ? ; VT_BYREF+VT_I4
pfltVal dword ? ; VT_BYREF+VT_R4
pdblVal dword ? ; VT_BYREF+VT_R8
pboolVal dword ? ; VT_BYREF+VT_BOOL
pscode dword ? ; VT_BYREF+VT_ERROR
pcyVal dword ? ; VT_BYREF+VT_CY
pdate dword ? ; VT_BYREF+VT_DATE
pbstrVal dword ? ; VT_BYREF+VT_BSTR
ppunkVal dword ? ; VT_BYREF+VT_UNKNOWN
ppdispVal dword ? ; VT_BYREF+VT_DISPATCH
pparray dword ? ; VT_BYREF+VT_ARRAY
pvarVal dword ? ; VT_BYREF+VT_VARIANT
byref dword ? ; VT_BYREF
cVal sbyte ? ; VT_I1 A 1-byte character value is stored in cVal.
uiVal word ? ; VT_UI2 An unsigned 2-byte integer value is stored in uiVal.
ulVal dword ? ; VT_UI4 An unsigned 4-byte integer value is stored in ulVal.
intVal sword ? ; VT_INT An integer value is stored in intVal.
uintVal word ? ; VT_UINT An unsigned integer value is stored in uintVal.
pdecVal dword ? ; VT_BYREF+VT_DECIMAL
pcVal dword ? ; VT_BYREF+VT_I1
puiVal dword ? ; VT_BYREF+VT_UI2
pulVal dword ? ; VT_BYREF+VT_UI4
pintVal dword ? ; VT_BYREF+VT_int
puintVal dword ? ; VT_BYREF|VT_uint
ends
VARIANT ends
Thanks, minor28, so anything VT_BYREF+??? would be qword in 64-bit?
VARIANT works also with pointers, so pointer size isn't same in x64 world.
MS double 64-bit, so size depends of it in 32-bit world.
The app was written with RadAsm3 32-bit about 10 years ago. I have not tried to develop the app for 64-bit.
Is this deja vu?
http://masm32.com/board/index.php?topic=7689 (http://masm32.com/board/index.php?topic=7689)
Just asking.
VARIANT STRUCT
vt WORD ?
wReserved1 WORD ?
wReserved2 WORD ?
wReserved3 WORD ?
Union
lVal SDWORD ? ; VT_I4
bVal byte ? ; VT_UI1
iVal SWORD ? ; VT_I2
fltVal REAL4 ? ; VT_R4
llVal QWORD ? ; VT_I8
dblVal REAL8 ? ; VT_R8
boolVal WORD ? ; VT_BOOL
scode DWORD ? ; VT_ERROR
cyVal QWORD ? ; VT_CY
date QWORD ? ; VT_DATE
bstrVal tPointer ? ; VT_BSTR ;----------------------------
punkVal tPointer ? ; VT_UNKNOWN
pdispVal tPointer ? ; VT_DISPATCH
parray tPointer ? ; VT_ARRAY
pbVal tPointer ? ; VT_BYREF|VT_UI1
piVal tPointer ? ; VT_BYREF|VT_I2
plVal tPointer ? ; VT_BYREF|VT_I4
pfltVal tPointer ? ; VT_BYREF|VT_R4
pdblVal tPointer ? ; VT_BYREF|VT_R8
pboolVal tPointer ? ; VT_BYREF|VT_BOOL
pscode tPointer ? ; VT_BYREF|VT_ERROR
pcyVal tPointer ? ; VT_BYREF|VT_CY
pdate tPointer ? ; VT_BYREF|VT_DATE
pbstrVal tPointer ? ; VT_BYREF|VT_BSTR
ppunkVal tPointer ? ; VT_BYREF|VT_UNKNOWN
ppdispVal tPointer ? ; VT_BYREF|VT_DISPATCH
pparray tPointer ? ; VT_BYREF|VT_ARRAY
pvarVal tPointer ? ; VT_BYREF|VT_VARIANT
byref tPointer ? ; Generic ByRef
cVal SBYTE ? ; VT_I1
uiVal WORD ? ; VT_UI2
ulVal DWORD ? ; VT_UI4
intVal SWORD ? ; VT_int
uintVal WORD ? ; VT_uint
pdecVal tPointer ? ; VT_BYREF|VT_DECIMAL
pcVal tPointer ? ; VT_BYREF|VT_I1
puiVal tPointer ? ; VT_BYREF|VT_UI2
pulVal tPointer ? ; VT_BYREF|VT_UI4
pintVal tPointer ? ; VT_BYREF|VT_int
puintVal tPointer ? ; VT_BYREF|VT_uint
STRUCT ; VT_RECORD
pvRecord tPointer ?
pRecInfo tPointer ?
ENDS
ENDS
VARIANT ENDS
Quote from: Caché GB on June 28, 2024, 09:56:56 PMIs this deja vu?
http://masm32.com/board/index.php?topic=7689 (http://masm32.com/board/index.php?topic=7689)
Just asking.
I swear, in both senses of the word, that I searched this forum and the old one and didn't find that.
:nie: