×
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 11/11/2010 10:21 AM, Nathan Andelin wrote:
To me a global declaration would be something that might be shared
across an entire activation group, which might include any number of
programs and service programs in a call stack.
To me, a global declaration would be something that's shared across the
entire globe. Maybe I'm weird :)
Seriously, though, following your line of thinking, stuff that's scoped
to the activation group should be called "activation-group-level", and
stuff scoped to the job should be "job-level".
Indeed, I've recently been in a conversation about environment variables
being scoped to the job (rather than system-wide as someone else thought.)
IMHO, when we use the term "global" it's not intended to be specific.
It just means "a wide scope" (and "wide" is a relative term!) When we
want to be more precise, we should mention the scope level, such as
"procedure-level", "job-level", "module-level", "actgrp-level", etc.
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.
midrange.com
