C / C++ / MFC

"Mark Salsbery", "cPallini" : PLEASE

14-Sep-08 2:25

You're welcome.
Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Joseph Marzbani13-Sep-08 22:13

Joseph Marzbani

13-Sep-08 22:13

Please reffer to 5 or 6 previous message and answer me ... I got your question and replied you

modified on Sunday, September 14, 2008 5:55 AM

Perspx13-Sep-08 22:36

13-Sep-08 22:36

First of all, please have a little patience.

These guys will answer you in their own time - they may be busy or away, and it is a Sunday. They, like all the other members on this site, are answering your questions voluntarily, and they have no obligation to do so, and are not being paid to do so either, so please show a little bit of respect and be thankful for the help they've already given you.

They will answer you in their own time if they have an answer to your questions.

Regards,
--Perspx

Don't trust a computer you can't throw out a window

-- Steve Wozniak

CPallini13-Sep-08 23:05

13-Sep-08 23:05

Thank you.
Smile | :)

Perspx13-Sep-08 23:12

13-Sep-08 23:12

No worries Smile | :)

Regards,
--Perspx

Don't trust a computer you can't throw out a window

-- Steve Wozniak

Mark Salsbery14-Sep-08 9:44

Mark Salsbery

14-Sep-08 9:44

Thank you from me as well Smile | :)

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

Perspx14-Sep-08 9:45

14-Sep-08 9:45

Your welcome Smile | :)

Regards,
--Perspx

Don't trust a computer you can't throw out a window

-- Steve Wozniak

CPallini13-Sep-08 23:07

13-Sep-08 23:07

I don't see any 'please' in your post's title...
Big Grin | :-D

Hamid_RT14-Sep-08 0:17

14-Sep-08 0:17

Does it necessary or no? Laugh | :laugh:

CPallini14-Sep-08 0:35

14-Sep-08 0:35

It's polite.
Smile | :)

Hamid_RT14-Sep-08 0:41

14-Sep-08 0:41

Title of his message is "Mark Salsbery", "cPallini" : PLEASE but I dont know he wants to serach about messages of Mark Salsbery and cPallini or he needs help of them? Wink | ;)

Perspx14-Sep-08 0:46

14-Sep-08 0:46

He modified the title. It was originally "Mark Salsbery", "cPallini" : Answer me ...

Regards,
--Perspx

Don't trust a computer you can't throw out a window

-- Steve Wozniak

Joseph Marzbani13-Sep-08 23:51

Joseph Marzbani

13-Sep-08 23:51

I really apologise for what I said and promise It won't happen again ...
I thank all you cool guys for your helps by now ...

IUnknown interface

George_George13-Sep-08 21:22

13-Sep-08 21:22

Hello everyone,

I am confused about one simple concept of IUnknown when reading some code,

1. Every coclass component must implement IUnknown, but not a must that every interface (which the coclass component implements) must implement IUnknown;

2. Every interface of every coclass component must implement IUnknown.

Which one is correct?

thanks in advance,
George

CPallini13-Sep-08 22:10

13-Sep-08 22:10

Every interface of every COM component must implement IUnknown since every interface is required to support interface navigation via QueryInterface.
Smile | :)

George_George13-Sep-08 23:09

13-Sep-08 23:09

Thanks CPallini,

Cool! I think your option is you agree with my option 2. Then another question, suppose my component implements interface IX and IY, and both IX and IY will implement IUnknown, so will there be diamond problem?

regards,
George

CPallini13-Sep-08 23:45

13-Sep-08 23:45

George_George wrote:
I think your option is you agree with my option 2.

Yes.

George_George wrote:
Then another question, suppose my component implements interface IX and IY, and both IX and IY will implement IUnknown, so will there be diamond problem?

Nope (a coclass is not a C++ class).
Smile | :)

George_George14-Sep-08 0:09

14-Sep-08 0:09

Thanks CPallini,

I think for the diamond issue I mentioned, you mean writing some code like this in my sample? The normal solution is providing one common implementation of AddRef/Release/QueryInterface in CFoo, so there is no diamond problem?

CFoo:IX, IY {// provide one common implementation of AddRef/Release/QueryInterface in CFoo, so there is no diamond problem?}

IX:IUnknown{}

IY:IUnknown{}

IUnknown{}

regards,
George

Hamid_RT14-Sep-08 0:16

14-Sep-08 0:16

See here[^].

George_George14-Sep-08 0:19

14-Sep-08 0:19

Thanks Hamid,

Looks like different from what CPallini said -- CPallini said every interface must implement IUnknown, but the wiki page mentioned every component must implement IUnknown -- "COM objects must minimally implement this interface"? I am confused.

Could you clarify please? Smile | :)

regards,
George

Hamid_RT14-Sep-08 0:33

14-Sep-08 0:33

I think here[^] and here[^] are good articles for you.

George_George14-Sep-08 1:52

Unusual memory leak ( code attached )

14-Sep-08 1:52

Thanks Hamid,

What is your conclusion of my orignial question? You agree with my point 1 of point 2?

regards,
George

Yanshof13-Sep-08 20:12

Yanshof

13-Sep-08 20:12

I have some memory leak in my code.
In my application i have some method that called every 5 seconds - and i found that my memory leak is in this method.
The leak increase the memory for 4kb every 5-10 seconds.

Attached the part of the code that i found that causing the memory leak.

void foo(const VARIANT FAR& Var1, const VARIANT FAR& Var2, const VARIANT FAR& Var3)
{
	COleSafeArray SafeV1, SafeV2, SafeV3;
	SafeV1 = Var1;
	SafeV2 = Var2;
	SafeV3 = Var3;
		
	int iNumObjs = SafeV1.GetOneDimSize();
	COleVariant vV1, vV2, vV3;
	for ( long i = 0 ; i < iNumObjs ; i++ )
	{
		CString  TempV1,Value;

		SafeV1.GetElement(&i, &vV1);
		TempV1 = vV1.bstrVal;
		
		SafeV2.GetElement(&i, &vV2);
		
		SafeV3.GetElement(&i, &vV3);
		Value = vV3.bstrVal;	
	}
}

Re: Unusual memory leak ( code attached )

CPallini13-Sep-08 23:19