Re: About String

[Robert A Duff <bobduff@shell01.TheWorld.com>]

Georg Bauhaus <rm.dash-bauhaus@futureapps.de> writes:

> Robert A Duff schrieb:
>> Maciej Sobczak <see.my.homepage@gmail.com> 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.  I really find it
>> annoying
>> 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 "=" or ";".

I suppose it's a matter of taste, at least in part.

But the situation in C-style languages is different -- declarations
don't stand out very well.  In Ada, the declaration syntax is clear
enough without adding "declare/begin/end".

Besides, even with "declare/begin/end", you still have to search all
over the place to find declarations -- they can be in various packages,
and in any outer block, procedure, etc.

> 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?

Not at all.  IMHO, "declare/begin/end" obfuscates, by pretending that
the stuff between declare and begin is just declarations, no executable
code.

> To me,  ad hoc variables between statements and Java classes fully
> named in source but without "import" at the head of the source file
> are similar in character.

They seem completely different, to me.  I agree with you that importing
without saying so up front is not good.

> The good news is: computers can help us with getting the
> necessary "paper work" (declare block etc.) done; use a
> good editor.

Sure, I do use a good editor.  That's not the point -- I'm not
complaining about how much work it is to type in "declare/begin/end" --
I'm complaining about how much work it is to _read_ that extra clutter.
The blocks of code we're talking about are often just 2 or 3 lines
of code, so adding several nested declare blocks can easily double
the size of the procedure.

- Bob