Okay, the two major ways I know of allocating memory are:
Type *pPointer = new Type[NumberOfTypes];
and
pPointer = (Type*)malloc(sizeof(Type));
are there any pros, cons, major differences between the two? I ask because I would like to see something done the first way, but then turn around and do it the second way but achieve the same results
i vote for new and delete
I'd say it all depends on the situation. There are a few different ways to use new to get your memory (like placement new, or custom memory pooling) to system specific calls like GlobalAlloc() in Windows. I wouldn't go as far as saying one is better than another, most of them do different things.
>are there any pros, cons, major differences between the two?
Wow, what a controversial subject. Well, here goes:
new/delete: These not only allocate blocks of memory, they also call constructors and destructors. In C++ this is a Good Thing.
malloc/calloc/realloc/free: These just work with uninitialized blocks of memory, you can get into more trouble more easily with these than new/delete (but not much).
I follow the guideline that if I'm using C I'll use malloc and family, and only with C. With C++ I prefer new and delete for most of my memory needs and the allocator class for everything else. C++ is all about convenience, so I make use of it. :D
-Prelude
Quote:
I follow the guideline that if I'm using C I'll use malloc and family, and only with C. With C++ I prefer new and delete for most of my memory needs and the allocator class for everything else. C++ is all about convenience, so I make use of it.
This is what you see in pretty much all the C++/C texts.
C++ new/delete
C - malloc/free
i pretty much use new and delete.. it is easier.. and less of hasels when freeing up...