(j3.2006) Specification part in every <block>, not just BLOCK?

Aleksandar Donev donev1
Thu Dec 21 18:29:39 EST 2006

On Thursday 21 December 2006 15:10, Van Snyder wrote:
> How about putting <specification-part> within <block>, so it's available
> in every construct?
While taking this C-like route is not technically impossible, I am still 
wondering why? What is difficult about writing BLOCK/ENDBLOCK where one needs 
to declare some additional variables? Sure, saving keystrokes is cute, but 
hardly Fortran like. Unless there is a better justification, I see little 
reason for creeping even in future revisions.
P.S. Recall that BLOCK itself was "creeped" via the macro feature, as it was 
realized declaring localized variables was most useful for macros.

More information about the J3 mailing list