Printable View
hi...
lets say i have a vector
std::vector<CMySocket> m_sMyConnectSocket;
later during some operation i resize it to 10...
after th usage of the vector...
i wanna reset it...
means bring it to a position it was when it was created...all empty..
how do i do it...
tks a lot:)
Code:m_sMyConnectSocket.clear();
tks a lot Mr.Masur..:)
Joseph, I recognized that you are very interested to work with vectors. So this article may help you in future.
:) Home wanted to post something but Home dont know what to post, So Home post in your thread...
Vector is here...:)
Joeseph..... :)
*PS: I said Bye, I meant to say bye to evil clones...There are a lot of clones on board but there are also alot of nice clones among those....I just dont like things to be planned in advance by Evil clones and those clones themselves....*
tks Mr.Sonu....
the moderator here really know their stuff....:)
i remember Mr.Masur also gave me this link/..
i am waiting for the 2nd part by Mr.Gabe.:)
tks
Hey, I also gave you superlink which will have lots of sublinks ans subsublinks...But you have not said a word of thanks... :(Quote:
Originally posted by Joseph_R_Thomas
tks Mr.Sonu....
the moderator here really know their stuff....:)
i remember Mr.Masur also gave me this link/..
i am waiting for the 2nd part by Mr.Gabe.:)
tks
didn't see...too busy reading the article by Mr.Gabe...;)
tks a lot....:):):):):):)
Okay:) You are welcome...:) :) :) :) :) :) :) :) :)
I know the feeling. I really, really, really, really, really, really, really, really know the feeling.Quote:
Originally posted by hometown
Hey, I also gave you superlink which will have lots of sublinks ans subsublinks...But you have not said a word of thanks... :(
Thank you for your understanding...:)Quote:
Originally posted by Sam Hobbs
I know the feeling. I really, really, really, really, really, really, really, really know the feeling.
Right : I know I'm going to be flamed for saying this but ....
Why are you using STL ?
Standard debugging of memory leaks in VC doesn't work with STL which means tracking them down is a nightmare.
There are plenty of classes in MFC which will do the same job.
Hmmm, I feel another thread coming on...
Darwen.
You do not need to have STL to break down the DEBUG_NEW you brought up in your other thread. This has nothing to do with STL. There is a lot of valid, non-STL that renders the DEBUG_NEW hopeless. I guess you wouldn't want us to use those coding constructs either, correct?Quote:
Originally posted by darwen
Right : I know I'm going to be flamed for saying this but ....
Why are you using STL ?
Standard debugging of memory leaks in VC doesn't work with STL which means tracking them down is a nightmare.
Regards,
Paul McKenzie
ONe way of saying is that the need of STL is suggested by Mr.Masur and Mr.Souldog..they have assessed my case and they felt it was needed...Quote:
Originally posted by darwen
Right : I know I'm going to be flamed for saying this but ....
Why are you using STL ?
Standard debugging of memory leaks in VC doesn't work with STL which means tracking them down is a nightmare.
There are plenty of classes in MFC which will do the same job.
Hmmm, I feel another thread coming on...
Darwen.
another way of putting is it tht i wanna learn to use it..:)
and as Mr.McKenzie said.............Quote:
Originally posted by Paul McKenzie
You do not need to have STL to break down the DEBUG_NEW you brought up in your other thread. This has nothing to do with STL. There is a lot of valid, non-STL that renders the DEBUG_NEW hopeless. I guess you wouldn't want us to use those coding constructs either, correct?
Regards,
Paul McKenzie
i wouldn't wanna use it either ;)