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 ;)
darwen using the STL (and especially the vector class instead of a linked list or something) will actually help cut DOWN on issues such as memory leaks. that said, they're just a part of programming and can still be dealt with.
use the stl, it's a tool. a good one.
i couldn't agree more
I get memory leaks so very, very, very seldom that I have no fear of them. Perhaps it is use of things such as the C++ standard classes that I rarely have memory leaks.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.
The STL is a coders greatest ally in the prevention of memory leaks. That and not being a sloppy and lazy programmer.
STL OR DIE!!!!!
cool dude...had too much STTL in the mornin' huh?:cool:Quote:
Originally posted by STL MAN
The STL is a coders greatest ally in the prevention of memory leaks. That and not being a sloppy and lazy programmer.
STL OR DIE!!!!!
Eerrr - what do you mean by that ?
If you mean that you can use vectors, then ok. But I have my own classes to do all of that anyway and they are all derived from MFC.
So in my opinion disadvantages of STL -
(1) It doesn't look very nice (if you look at STL-code and the equivalent non-STL then the STL looks really messy).
(2) Can't do memory tracking etc on it.
(3) Can't inherit which means going around the houses most of the time.
Advantages of STL :
(1) Sorting.
(2) Lower (not by much in my opinion but there you go) overhead since no inheritance from CObject.
Sorry, I didn't intend for this to turn into a flaming match. I meant for it to be a real discussion of the pros and cons of STL Vs MFC. My opening statement was intended to be antagonistic but that was to get it going.
In the end this isn't really going to change anything. You'll still use STL and I'll still use MFC because we'll both be using tools we like.
In fact its rather nice that we do have a choice don't you think ?
Darwen.
Oh and saying that 'I rarely get memory leaks' is fine. But what happens when you DO get one ?
I also write all by code in a constructor/destructor way and rarely get memory leaks.
But on the occasions that I do it's really, really nice that I can track down where they are and nuke them.
You do not have the option.
Darwen.
Okay...since we are far way from the original topic here already, I would kindly like to ask everybody to post relevant opinions to the discussion STL vs. MFC in the dedicated thread...
Thank you very much.
I don't need it.Quote:
Originally posted by darwen
You do not have the option.
I've already asked you why you think this is so in your other thread, maybe you should step into the MFC code and see what it acutally uses to track memory leaks, maybe it will open your eyes to the fact that MFC's memory tracking uses the CRT. Maybe you should look a little deeper than just MFC. And BTW it's overkill, 2 lines of CRT calls, 1 macro, and that's all I need to find memory leaks (ok maybe 1 more when I do find one that falls into malloc/free)...Quote:
Originally posted by darwen
(2) Can't do memory tracking etc on it.
(Darwen.
So please expand on your #2 cause I have the TP handy :)
And they have not been peer-reviewed by ANSI, so why should any of us use them? How do we know your classes aren't full of bugs? Are you now saying that Joseph (the OP) should start using your classes (or code his own)? You are talking about the merits of MFC, and then you state that you still need to write your own functions -- more code to maintain, more potential bugs.Quote:
Originally posted by darwen
But I have my own classes to do all of that anyway and they are all derived from MFC.
Also, I highly doubt that the number of functions you have written come anywhere close to what is provided by the STL container and algorithm functions.
As I stated before, the problem that you are having doesn't seem to be STL, but template syntax in general. You can code a non-STL application, and it will look messy to you since it may use templates.Quote:
So in my opinion disadvantages of STL -
(1) It doesn't look very nice (if you look at STL-code and the equivalent non-STL then the STL looks really messy).
Why would you need memory tracking for the STL containers? The containers already work. The only memory tracking you would need would be on your own classes.Quote:
(2) Can't do memory tracking etc on it.
I don't know what you mean by "going around the house". Ever hear of generic programming? You don't accomplish that by inheritance, but by template programming.Quote:
(3) Can't inherit which means going around the houses most of the time.
Sorting is just one example. Have you seen the list of algorithm functions? How about searching? How about calling a function on all elements of the container? MFC has no such functions. Have you ever used iterators? I think you need to take a look at STL in its entirety.Quote:
Advantages of STL :
(1) Sorting.
This has been rehashed time and again on different forums. MFC (in terms of the container classes) has always been deemed inferior to STL by most, if not all, C++ professionals who have name recognition. Sorry, but that's the consensus.Quote:
Sorry, I didn't intend for this to turn into a flaming match. I meant for it to be a real discussion of the pros and cons of STL Vs MFC
Regards,
Paul McKenzie
As mentioned...we are far way from the original topic here already, so the discussion about STL and MFC can be continued in the dedicated thread...
Thread is closed.