Re: IDL questions
1. Scripts have no relation whatsoever to your IDL. You can
use whatever variable names you want in your script. They
all have a single type - variant.
2. No, it specifies the direction of marshaling. Missing marshaling
direction attribute causes MIDL to assume [in].
3. See 2 above. [in] means into the method, [out] means out
of the methoid, [in, out] means in both directions.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"nly" <nlyee2001@yahoo.com> wrote in message
news:O1cUBfJ6GHA.3452@TK2MSFTNGP05.phx.gbl...
1. Given the following IDL code snippet:
[object, uuid(00000000-3004-0000-0000-00609785B4C4),
dual, helpstring("IModString Interface"),
pointer_default(unique)]
interface IModString : IDispatch
...
Will the object name in a scripting environment be "IModString Interface"?
Or where should the name go in IDL code?
2. When a parameter has attribute like [in, out], it means that this
parameter needs marshalling; without such [...] attribute, it means not.
Is
this correct?
3. What're difference between [in], [out], and [in, out] in 2?
Thanks in advance!