Re: 'Lets' organize our Delphi code
- From: "m. Th." <a@xxxxx>
- Date: Wed, 25 Jun 2008 21:00:59 +0300
Rudy Velthuis [TeamB] wrote:
m. Th. wrote:
Do you think that you'll have problems understanding what is written
here:
for i: integer = 1 to 100 do
ShowMessage(IntToStr(i));
?
I think I have already said that, as single appearance, they are not a
problem. They become a problem if code gets interspersed with various
inline variable declarations in various spots.
For the same reason I don't like the inline definition of methods in
Java and C#(*), I don't like the inline declaration of variables in
these languages. I love to have my method declarations in the interface
section and the method definitions in the implementation section. In
the same way, I love my variables in the var section and the code using
them in the begin-end block.
(*) And what I thoroughly hate is having the private data members
somewhere at the bottom of the class declaration, but the code using
them near the top, which is possible in languages like Java, C# and
C++, AFAIK.
Yep, about this usage pattern we agree. :-)
--
m. th.
.
- References:
- 'Lets' organize our Delphi code
- From: m. Th.
- Re: 'Lets' organize our Delphi code
- From: John Herbster
- Re: 'Lets' organize our Delphi code
- From: m. Th.
- Re: 'Lets' organize our Delphi code
- From: Marco van de Voort
- Re: 'Lets' organize our Delphi code
- From: Rudy Velthuis [TeamB]
- Re: 'Lets' organize our Delphi code
- From: m. Th.
- Re: 'Lets' organize our Delphi code
- From: Rudy Velthuis [TeamB]
- 'Lets' organize our Delphi code
- Prev by Date: Re: Response a negative view about Delphi
- Next by Date: Re: Response a negative view about Delphi
- Previous by thread: Re: 'Lets' organize our Delphi code
- Next by thread: 'Lets' organize our Delphi code
- Index(es):
Relevant Pages
|
