RE: compiling an RPGLE pgm

I'll admit it, I was guessing--one class in 8086 Assembler probably doesn't
make me a compiler expert. <g>  I didn't mean to imply that OPM and ILE used
different static memory models.  I didn't realize that dynamic memory
allocation was available in OPM.   

I'm curious if the following is a good description of static data in both
OPM and ILE:
Constants, global variables (including file fields,) compile time array
data.

The OPM use of automatic storage is interesting too.  

> -----Original Message-----
> From: Barbara Morris [mailto:bmorris@xxxxxxxxxx]
> Sent: Tuesday, April 22, 2003 9:37 AM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: Re: compiling an RPGLE pgm
> 
> 
> Joel Fritz wrote:
> > 
> > IIRC, programs compiled in the Default Activation Group use 
> the old style
> > static memory model.  When you're compiling DFTACTGRP(*NO), 
> among other
> > things you're enabling your programs to use automatic 
> variables and heap
> > memory which are necessary for subprocedures.
> > 
> 
> Joel, DFTACTGRP(*NO) programs use the same static memory 
> model, although
> the way the static storage is reused by the system does 
> differ(*).  Even
> DFTACTGRP(*YES) programs have some automatic storage used for 
> compiler-generated stuff.  Heap storage is available for 
> DFTACTGRP(*YES)
> programs via ALLOC, REALLOC etc.
> 
> (*) I'm not completely clear on the details of how the static 
> storage is
> reused.  If I recall correctly, when RCLRSC is done, the 
> static storage
> for DFTACTGRP(*YES) programs is made available to the system.  For
> DFTACTGRP(*NO) programs (not srvpgms, though) running in the dft AG,
> their storage is not reclaimed, but is just marked as needing
> initialization next time the program is called.  When DFTACTGRP(*YES)
> RPG programs end with LR on, the static storage is also 
> released back to
> the system.
> 
> 
NOTICE:
All e-mail sent to or from this e-mail address will be received or otherwise
recorded 
by The Sharper Image corporate e-mail system and is subject to archival, 
monitoring, review by and/or disclosure to Sharper Image security and other 
management. This message is intended only for the use of the addressee and
may 
contain information that is privileged and confidential. The contents of
this message 
may contain personal views which are not the views of The Sharper Image. If
you are 
not the intended recipient, dissemination of this communication is
prohibited.