just running some quick COM code in perl and I notice this: if I call a
property or method that returns VT_I4, Win32::OLE maps that to a perl
integer in scalar context. When I call a property or method that
returns VT_INT, however, it gets mapped to a perl string. Is this
deliberate? Is it
On Wed, 09 Jan 2008, Michael Ellery wrote:
just running some quick COM code in perl and I notice this: if I call
a property or method that returns VT_I4, Win32::OLE maps that to a
perl integer in scalar context. When I call a property or method that
returns VT_INT, however, it gets mapped to a
Jan Dubois wrote:
On Wed, 09 Jan 2008, Michael Ellery wrote:
just running some quick COM code in perl and I notice this: if I call
a property or method that returns VT_I4, Win32::OLE maps that to a
perl integer in scalar context. When I call a property or method that
returns VT_INT, however,
On Wed, 09 Jan 2008, Michael Ellery wrote:
The VT_TYPE coming into my put_Some_VARIANT_Property was actually
VT_BSTR in this case, which I was not expecting. Simply wrapping int()
around the get call works fine, but a fix to Win32::OLE would be great.
I think I'll also update my VARIANT
