| T O P I C R E V I E W |
| obricker |
Posted - Jul 31 2006 : 3:38:47 PM
I could not find this mentioned already so here it is.
Using: Move Implementation to Source file on methods such as the following:
STDMETHOD(Cancel)()
{
// Add your function implementation here.
return E_NOTIMPL;
}
does create an implementation in the source file:
STDMETHODIMP CMultiPathTracker::Cancel()
{
// Add your function implementation here.
return E_NOTIMPL;
}
but it also causes the declaration to be removed from the header.
Otis |
| 4 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Aug 08 2006 : 01:18:00 AM
Fixed in build 1531. |
| feline |
Posted - Aug 01 2006 : 6:39:40 PM
this is definitely a bug, and a relatively nasty one. i just wanted to make sure there was only one bug, and not two 
case=1923 |
| obricker |
Posted - Aug 01 2006 : 09:06:37 AM
The implementaion is fine. You are right that VAX must know something about the STDMETHOD/STDMETHODIMP pairings. The only problem is that it should be leaving:
STDMETHOD(Cancel)();
in the header but doesn't. All trace of the method is removed from there.
For now, I am just copying the declaration line before Calling Move Impl and adding the ;. It is still a bit easier than doing everthing by hand. But it does seem like a bug.
Otis |
| feline |
Posted - Jul 31 2006 : 5:46:41 PM
i am seeing the same problem here. personally i do not know about COM, so is the generated implimentation sensible?
STDMETHOD has been replaced with STDMETHODIMP which suggests VA knows something about these #define's
using alt-g on them suggests this is sensible, but i am not certain this is right. |
