× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 9/26/2012 3:31 PM, Ken Sims wrote:
Hi Alan -

On Wed, 26 Sep 2012 13:54:32 -0600, Alan Campin<alan0307d@xxxxxxxxx>
wrote:

Yes, but only the first time, if the variable is global, that a given
module or program is called. In my opinion, that is a bug. I think
every time you call a program or module it should execute the
initialize logic for a global variable if the variable has a INZ
keyword on the variable.
Not even!!!

I have many API-type programs that get called repeatedly and return
with *INLR off. If the global variables were reinitialized (even if
it was limited to those with an explicit INZ), many of those programs
would stop working properly.

The rule of the compiler is that global variables are static,
regardless of whether or not there is an explicit INZ. Changing that
rule would be a major issue for many people.

To get your behavior there would need to be an enhancement to allow
global variables to be specified as AUTOMATIC. If that were added, I
would expect those variables to be initialized on every call, even if
they don't have an explicit INZ.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.

I have to chuckle when I read that sig, Ken. And I agree 100% with your assessment about only changing the rules with an AUTOMATIC flag. However, many might argue that I am not right in my mind, so there you go.

Joe

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.