Global vs Local behaviour

[DrD]

The use of a command line entry "global" variable would make the contents available for other activities when a program concludes. As implemented, there is a problem with this reasoning, because a program that passes a value in via the command line, automatically makes that input variable "local" in context. Here is an example:

Code:


EXPORT stg:="DRD";
EXPORT str()
BEGIN      
  return stg;
END;

The global variable retains its programmed contents, remaining available at the end of run time. Suppose its desired to pass parameters via the command line:

Code:


EXPORT stg;
EXPORT str(stg)
BEGIN      
  return stg;
END;

In this example, the global variable, stg, gets displaced by a local (same name) variable during input. Any programmatic effect on stg vanishes once the program terminates. If the "command line input" were to initially check for the 'global' existence of its variable, I think it would enhance the process of parameter passing via the command line.

What do other users think about this?