|
That's the way it seemed to me. I didn't try it in a named activation group, but the way it behaved after signing off then signing back on made me think activation group. I'm willing to accept that that's the way it works and code accordingly. I'm curious why it was designed that way. I guess I think of a static variable's lifetime in terms of the way I learned about them in C on the PC nearly 10 years ago. Once the main program ended, all _properly managed_ memory was returned to the operating system and the static variable started with its initialized value at each call to the main program. > -----Original Message----- > From: pytel@us.ibm.com [mailto:pytel@us.ibm.com] > Sent: Wednesday, November 15, 2000 7:52 AM > To: RPG400-L@midrange.com > Subject: Re: lifetime of a static variable > > > > Lifetime of ILE static variables by architecture is the lifetime of > activation group. > For example, for *DFTACTGRP this means until the end of the job. > > Alexei Pytel > > +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.