|
Joel Fritz wrote: > > 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. > Joel, by "OPM", do you mean DFTACTGRP(*YES) programs? If so, I wouldn't use the term that way - maybe "OPM equivalent" would be better. "Real" OPM RPG (RPG III) doesn't have dynamic memory allocation and if I recall correctly, the OPM RPG compiler doesn't generate any automatic variables (but it could - OPM CL does). For any RPG program, RPG III or RPG IV, static data includes global variables, and many internal control structures. For ILE RPG programs with subprocedures, it also includes local variables defined with STATIC. For RPG IV programs (both flavours of dftactgrp) I don't think constants (including compile-time data) is part of the static data. If you display an ILE module or program (any language), there's an item called the "String Directory". I'm pretty sure this is where the constants are. I have no idea what kind of storage is used.
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.