🚀 go-pugleaf

Darren Walker (dwalker@imtn.dsccc.com) wrote:

: IMHO, I have found the memory allocation shemes for C++ to be VASTLY
: superior to those of C. Using a new example, expanded on from above...the
: realloc issue...(or free issue for that matter.)

: class TApplication
: {
: public:
:     TApplication(char *name);
:     ~TApplication();
:     ...(lots of other crap not needed for example)...
: private:
:     char                 *name;
:     LinkedList           *Head;
:     BinaryTree           *Root;
: };

: TApplication::~TApplication()
: {
:     if(Head)
:         delete Head;  // this will recursively delete the entire list (if
:                       // the list's destructor is set up right.
:     if(Root)
:         delete Root;  // this will recusively delete the entire tree.
: }

A recursively called delete_linked_list() function would work just as
well.

:  
: .
: .
: .
: TApplication* MyApp;
: MyApp = new TApplication("My Application");

: // now we want to RE-ALLOC MyApp
: if (MyApp)
:     delete MyApp;  // that's it...C++ class destructors take over and no
:                    // memory leaks occur!
: MyApp = new TApplication("My Application Again!");

This is NOT how realloc works.  Realloc is used to increase or decrease
the size of an array WITHOUT changing the contents.

: Now, IMHO, this seems FAR superior in both concept and implementation than
: having to first remember to call the deallocator for the linked list, then
: calling the deallocator for the binary tree, explicitely, before reallocating
: MyApp. Maybe this will explain why us C++ programmers have FAR fewer memory
: leaks than C programmers. It's because we choose to let the natural design
: of the language do the job it was meant for. So ANYONE who says new and
: delete are useless, has no clue about C++, and should stick with C, as they
: completely missed the whole point behind the newer, more powerful language.

The allocation and deallocation of memory can easily be done within a
C function.

MyApp = new_TApplication("My Application");
delete_TApplication(MyApp);

You also completely missed the point of realloc.  Your "example" of how
to realloc in C++ actually doesn't change the size of the memory block
and is thus totoally irrelavent.

--
+----------------------------------------------+
|    Rainer Deyke (rainer@mdddhd.fc.hp.com)    |
| "The Earth shall inherit the meek" - Carcass |
+----------------------------------------------+