(j3.2006) Public Comment J32036 (Submodules)

[Michael Ingrassia]

It looks to me as though there are two points in J32036 that need
specific responses.

>public review is
>just as important for TRs as for whole revised standards.

This seems like an important issue.  Surely when next we are tempted to
issue an important feature as a TR, we want it to be thoroughly
scrutinized through public comment at the point in its life cycle where
comments can do some good?


>As for the third of the "advantages" of submodules, nesting
>of scopes to any depth, is something that I believe the
>language shouldn't support.

Setting a definite limit in nesting depth (looks like 3 would
handle the examples in ISO/IEC TR 19767:2004(E) ?)
would promote portability, if as I expect every implementation will have
some nesting depth which is practically unattainable, just as DO loops
may not be infinitely nestable.

      --Michael I.