RE: dealloc (Correction)

If the based pointer already pointed to an allocate memory, shouldn't
you dealloc it first before calling subprocedure that return a pointer?
Otherwise you might cause memory leak (I think).  

The compiler checking I'm referring to is more like in the source code
you do something like this: myField_BasePointer = *null;  (from
everybody's posting, seems like you should always do dealloc(n)
myField_BasePoniter)
 
I'm really not too worry about the based pointer pointing to an invalid
address (May be I should).  I'm more concerned about the memory leak
(Memory is cheap, may be I just worry too much.  Then again, Chirs just
should us a few lines of code that could allocated 300+ GB of memory
:)).



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
AGlauser@xxxxxxxxxxxx
Sent: Thursday, December 07, 2006 1:14 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: dealloc (Correction)

Lim Hock-Chai wrote on 07/12/2006 02:09:02 PM:

Good point, Scott.  From everybody's posting, seems like there is 
really no reason to ever set based pointer to *null by assigning *null

to it.

Sure there is.  If I call a subprocedure that is supposed to return a
pointer to an object, it should probably return *null if it can't find
the object for some reason.  If I wrote such a subprocedure, I'd have a
strong argument for setting a pointer to *null.

In fact, pointers which point to  deallocated memory should probably be
set to null all the time (as Barbara said early, IIRC).  That way, you
*always* get an error if you try to reuse that pointer later in the code
without resetting it to point to valid memory, instead of just maybe
getting an error.

########################################################################
#############
Attention:
The above message and/or attachment(s) is private and confidential and
is intended only for the people for which it is addressed. If you are
not named in the address fields, ignore the contents and delete all the
material. Thank you. Have a nice day.

For more information on email virus scanning, security and content
management, please contact administrator@xxxxxxxxxxxx
########################################################################
#############
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.