| William M. Klein 2008-03-15, 3:56 am |
| Actually, ISO (ITTF specifically) is very careful about the use of "NOTE". By
definition, in an ISO Standard anything included in a "NOTE" (or an example) is
"non-normative". Therefore, the point of that NOTE is "informative" and is
simply confirming the fact that there is NO normative text telling implementers
what they are required to do with storage when a CANCEL occurs.
If you are interested in the ISO drafting rules, I think I can find an online
reference for you. (It deals with things like "notes"; use of "can" "may"
"shall" "will" etc)
--
Bill Klein
wmklein <at> ix.netcom.com
"Robert" <no@e.mail> wrote in message
news:hg4mt3trr84aqck56d2lrp6r6jj4obnhbc@
4ax.com...
> On Fri, 14 Mar 2008 14:29:05 GMT, "William M. Klein"
> <wmklein@nospam.netcom.com> wrote:
>
>
> The question for THIS particular thread is whether "The standard says
> working-storage is
> allocated statically." versus whether working-storage items can be reallocated
> dynamically
> while the program is running.
>
> The standard calls them "static items" without defining the phrase.
> Dictionaries define
> static and its Latin root statis as motionless, fixed. It seems clear to me
> that a static
> data item is one whose address does not change during the item's life. By
> contrast, a
> dynamic item is mobile in memory.
>
>
> The 02 standard says under CANCEL:
>
> "NOTE It is neither prohibited nor required that the storage of the specified
> program be
> freed by the execution of a CANCEL statement."
>
> I wish standards writers didn't embelish substantive statements with "note",
> giving the
> impression the statements are parenthetical asides. ISO should employ copy
> editors to
> clean up awkward techie writing style.
|