Re: RW on Working-Storage (was: J4 - presentation/discussion on "Future of the C

On Thu, 13 Mar 2008 06:28:30 GMT, "William M. Klein" <wmklein@nospam.netcom.
com> wrote:

>I can certainly understand the confussion but calling something "static dat
a"
>(and defining what that means does NOT mean that the storage is allocated
>statically (which was your statement).

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. Fo
rget automatic
and initial, concentrate on what the standard says about static.

>The section that you quoted from is
>under
>
>  "8.6.3 Automatic, initial, and static internal items"
>
>The first paragraph explains what all of this is about, i.e.
>
>"Each internal item has one of the three persistence attributes: automatic,
>initial, or static. The designation of automatic, initial, and static items
>relates to their persistence and the persistence of their contents during t
he
>execution of the run unit."
>
>Notice inparticular that for "automatic" data, it says,
>  "Their storage is allocated and set to initial state each time the runtim
e
>element containing them is activated."
>
>For "static" items, the statement is quite different.  It says,
>
>"They are allocated no later than immediately before initialization"
>
>Which I think (to me) is NOT what you said, i.e.
>
>" The standard says working-storage is allocated statically."

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 lo
ad time.'  I
said "working-storage is allocated at program load time." There is no confus
ion.


>Bill Klein
> wmklein <at> ix.netcom.com
>"Robert" <no@e.mail> wrote in message
> news:lr3ht3pi8lejvamj0qjgpfdbdqo88336s6@
4ax.com... 
>