| Richard 2008-03-13, 6:56 pm |
| On Mar 14, 3:14 am, Robert <n...@e.mail> wrote:
> On Thu, 13 Mar 2008 06:28:30 GMT, "William M. Klein" <wmkl...@nospam.netcom.com> wrote:
>
>
> The problem with abstract sounding language is that peoples' eyes glaze over and they
> forget the original question. Let's try to stay focussed on one question -- plain vanilla
> working-storage. Of the three choices below, it is the one called static. Forget automatic
> and initial, concentrate on what the standard says about static.
>
>
>
>
>
>
>
>
>
>
>
>
> Initialization means at program load time. Statically also means at program load time. In
> plain English, the standard says 'working-storage is allocated at program load time.' I
NO, Robert, that is your _INTERPRETATION_ of what you think it means.
> said "working-storage is allocated at program load time." There is no confusion.
>
NO, Robert, that is simply the same _INTERPRETATION_ of what you think
it means.
When you make a mistake you merely repeat it until everyone gives up.
(and then later claim that you were right anyway).
If my program, loaded and running, CALLs a subroutine for the first
then it will create a new working-storage for that. When I CANCEL it
will destroy that area and make it available for reuse by another.
This could happen even if the program was linked so that the program
code loaded with the run unit.
In OO COBOL a new object will dynamically create a new working-storage
for itself.
|