🚀 go-pugleaf

Colin B Maharaj wrote:

> If you are using the heap, then you will use a pointer instead .
> The code will look like this....
> 
> char *s = new char [80];
> 
> or
> 
> char *s;
> s = new char [80];
> 
> WARNING WARNING WARNING......
> 
> Whenever you use memory from the heap you must manually give it back
> to the operating system like this.....
> 
> delete s;
> 
> If not you get a memory leak and could mess up windows.
> 
> remember for every new you must have a corresponding delete.


More important!

If you allocate an array using the array form of new [], you must
return that memory with the array form of delete [].

i.e.
char *s = new char [80];
delete [] s;

You get undefined behaviour if you call delete on an array allocated
with new[].

I know MS choose to define the behaviour as being smart for you, so you
don't even notice the bug.  I believe that with Borland you are
probably corrupting the memory manager, which will give subtle and
strange bugs in a totally different part of your application at some
point in the future.

Other than that, good advice <g>

AlisdairM(TeamB)