|
I was thinking the opposite. Since RPG compiler usually do this type of things (you know auto initial alpha and numeric file, auto open file....) for RPG programmer, I kind of except the compiler to know to generate code to dealloc the memory automatically when the program set the based pointer to *null. Wishful think ... :) -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris If I recall correctly (and I should, since this was my doing), the reason for not always setting the dealloc'd pointer to null was to try to force RPG programmers to be a conscious of the need for clearing the pointer after deallocation. If it was always just that one pointer variable that had the address of the allocated storage, there would be no issue, but a programmer should be aware of any other variables that should also be cleared.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.