×
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.
IMHO, one big advantages of introducing subprocedures to existing programs
is the fact that as long as the variables used in the subprocedure are
either passed in or defined locally then there is no chance that
coupling-related issues [such as inadvertently stepping on global values]
will arise...
;-)
"James H. H. Lampert" wrote in message
news:mailman.3432.1388168538.2717.rpg400-l@xxxxxxxxxxxx...
A couple of things on the "leave well enough alone" side:
1. It's entirely possible that (perhaps without anybody realizing it) a
program might very well *depend* on side effects of a subroutine playing
around with global variables, and if one switches to local variables,
eliminating the side effects, one could break whatever depends on them.
I've seen it happen. Usually the tipoff for something dependent on a
side effect is when it works even though it looks like it shouldn't.
2. Remember: when you have OPM and ILE calling each other across
activation groups, you have an "impedance bump," but when you have ILE
actually doing ILE things (like procedure calls) in the OPM activation
group (usually only when it's set to run in CALLER, and is then called
from an OPM program), you can end up with erratic behavior. (I try to
avoid situations like that on anything I let out of the building.)
--
JHHL
midrange.com
