Re: I am not sure any more...
@19, your post doesn't even make sense. I cannot fathom where you got the idea that if someone doesn't use OOP their program will die or fail sometime in the future. That has to be one of the dumbest things I've read. GCC is written in C, and various other languages, including C++, but most of which are non-object oriented languages, and its still going strong. The linux kernel is wrotten in C and assembly, no C++ anywhere, and its been going strong since 1991. You know what's even more ironic? GCC started out in C, and was released in 1987, and its been going strong for the past thirty-one years. The entire POSIX interface is C, and its going strong. Most of the tools you use in your everyday computing life (especially those in the command line) are written in C. The "most" is about 30-50 percent, at least. So I really, really don't understand where you got the absurd idea that if someone doesn't use OOP, their program will die. What about functional programming? How about imperative, declarative, structured, function-level, logic/rule-based, constraint, aspect-oriented, and reflective programming? What about all the other programming paradigms that I haven't listed?
Alas, I digress. And that part of "advanced memory management"? You do realize that most professional programming books (including my favorite) tells you -- more than once, too -- to use the STL to manage memory, and to avoid manual memory allocation if possible? I can think of only a few cases where I've ever had to manually allocate memory, and all of those involved interacting with C libraries (and there are probably ways that I could do it with the STL but I couldn't think of a way to do it with the STL at the time, or couldn't find a way). My favorite book, professional C++, states (as a warning), in regards to memory management...
In modern C++ you should avoid low-level memory operations as much as possible in favor of modern constructs such as containers and smart pointers!
And this, as a warning, too...
It is strongly recommended to use smart pointers as often as possible to avoid memory leaks.
So yep, there you go, the words of Marc Gregoire, right out of the book. Of course there are those times where you have to use new/delete, but those times (for me, anyway) are rare and far between. So, I still say that someone who is new to C++ does *not* need to know much, if anything at all, about the low-level methods of allocating memory with new/delete. And definitely not the OP, since the OP never was even asking about memory management or C++ at all. So, can we stop derailing this topic with the useless nonsense I just proved as useless nonsense and get back on track with helping the OP?
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
