On Jun 9, 6:00=A0am, Georg Bauhaus <rm.dash-bauh...@[EMAIL PROTECTED]
>
wrote:
> Robert A Duff schrieb:
>
> > Maciej Sobczak <see.my.homep...@[EMAIL PROTECTED]
> writes:
>
> >> You did not state it explicitly, but I presume that you allow mixing
> >> declarations with executable code ("as in Java and other languages")?
>
> > Yes, if I ran the circus, I would allow that. =A0I really find it
annoyi=
ng
> > that I have to add 3 useless lines of code (declare/begin/end) and an
> > extra level of indentation, when all I wanted to do was declare
> > a very-local object.
>
> I find it annoying when I have to search other people's
> procedures for variables. A typical sequence of statements is
> sprinkled with declarations (Java, C, Perl, ...) and no oher
> indication of the newly introduced variables other than
> two identifiers before "=3D" or ";".
>
> As Dmitry says, there is an *implicit* scope only.
> When I'm up the wall I speculate whether this viewpoint on language
> use is driven by a desire to achieve income by obfuscation?
> The tempting quick hack?
>
> To me, =A0ad hoc variables between statements and Java cl***** fully
> named in source but without "im****t" at the head of the source file
> are similar in character.
>
> The good news is: computers can help us with getting the
> necessary "paper work" (declare block etc.) done; use a
> good editor.
I very much agree. The requirement for an explicit declaritive region
is a very good thing for reasons of readability and maintainability.
If variables could be declared anywhere in a procedure then it really
would be a circus.
- Britt
|
