Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bad ideas for Delphi's future

10 views
Skip to first unread message

Skybuck Flying

unread,
May 14, 2013, 10:11:01 PM5/14/13
to
Hello,

Macro has some bad ideas about Delphi's future:

http://delphi-insider.blogspot.nl/2013/04/new-delphi-xe4-white-paper-delphi.html#!/2013/04/new-delphi-xe4-white-paper-delphi.html

http://embt.co/DelphiWP

1. With statement to be removed (totally crazy):

"
Sooner or later, the with statement is going to be deprecated and removed
from the Delphi language. You can easily start removing it now from your
code, and most Delphi developer will
agree this is a good idea anyway, given some of the hidden pitfalls of this
keyword.
"

Apperently this guy rather writes a million times:
SomeClass.SomeDeeperClass.Some.Bla.Bla.Bla.Bla

instead of

with SomeClass.SomeDeeperClass.Some.Bla.Bla.Bla do
begin
Bla;
Bla
Bla;
end;

The with statement is a very powerfull future of the Delphi language which
C++ programmers can only dream of... removing the with statement would be a
big mistake.

Every Delphi programmer is well aware of any potential pitfalls, add new
language features to solve any pitfalls if at all necessary, but don't
remove a brilliant language feature.

2. Remove pointers (Java dejavu anyone ? Clearly crazy).

"Reduce or remove pointer usage, given direct usage of pointer is being
discouraged as we move towards some automatic memory management. Using
generic container classes, instead of TList (internally based on pointers)
is a good example of the migration that the Delphi RTL library is
undergoing, and we suggest that Delphi developers perform similar
conversions in their code as well."

Clearly Macro has had his head (lol many h's:)) up .NET for far too long.
Not all algorithms can be build with Tlists and crap like that. Some of the
best require basic types and some hard manipulation. Pointers, integers,
typecasts, records, all of these low level language features should stay to
allow maximum powerfull expression of low level ideas/algorithms. Removing
pointers would be a major/big mistake, don't repeat java's mistakes please.

3. Remove assembly (totally crazy)

"
Remove assembly code, as this isn't portable to the new compiler and isn’t
applicable to ARM CPUs.
"

Instead of removing it, add some nice ARM assembler to the Delphi compiler.
Enough said ;) :)

Bye,
Skybuck.

0 new messages