Re: State of WORKING-STORAGE in Statically-Called Subroutines
From: Howard Brazee (howard_at_brazee.net)
Date: 12/18/03
- Next message: docdwarf_at_panix.com: "Re: State of WORKING-STORAGE in Statically-Called Subroutines"
- Previous message: Howard Brazee: "CoBOL moved to OO"
- In reply to: docdwarf_at_panix.com: "State of WORKING-STORAGE in Statically-Called Subroutines"
- Next in thread: docdwarf_at_panix.com: "Re: State of WORKING-STORAGE in Statically-Called Subroutines"
- Reply: docdwarf_at_panix.com: "Re: State of WORKING-STORAGE in Statically-Called Subroutines"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 18 Dec 2003 14:56:53 GMT
Boy it is much easier when there is no good reason to have any static calls.
If everything is dynamic, then everything is the same version.
I work at an environment where Endevor compiles all programs before they go into
production - and overrides the parms that are put in the source even. It does
mean that I can't optimize the sort when told that I can. But it also means
that we don't accidentally have a static call.
If the shop compiler requires static calls, we are in a bit more danger - not
only because different programs may be compiled with different versions of the
program, but because programmers can force dynamic calls by calling variable
names.
I have seen this variable name calling as shop standards in many locations.
- Next message: docdwarf_at_panix.com: "Re: State of WORKING-STORAGE in Statically-Called Subroutines"
- Previous message: Howard Brazee: "CoBOL moved to OO"
- In reply to: docdwarf_at_panix.com: "State of WORKING-STORAGE in Statically-Called Subroutines"
- Next in thread: docdwarf_at_panix.com: "Re: State of WORKING-STORAGE in Statically-Called Subroutines"
- Reply: docdwarf_at_panix.com: "Re: State of WORKING-STORAGE in Statically-Called Subroutines"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|