Around the web: Delphi code becoming unwieldy?
"With the last iterations, I've got the feeling that Delphi code is becoming more and more unwieldy, verbose and, well, bloated.
When I say "Delphi", I mean "Delphi", other Pascal dialects have introduced more elegant forms (Prism/Oxygen especially), and have at the very least tried to fight entropy.
Just a few examples:
- anonymous methods syntax is ugly and verbose, it is very dependent on strict formatting for readability, and even then, there doesn't seem to be much in the way of standard readable formats for it), a short syntax-sugared form (as in lambdas) would help
- the newly required scoped enums for FMX result in unwieldy and hard to read code (especially when used in sets).
- unit prefixes in XE2 are unwieldy and verbose, they should have introduced Java or C#-like syntax to keep things readable, along with ability to maintain the "uses" automagically
- RTL generics classes have complicated names and still manage to be quite ambiguous (mixing types of all sort in a big naming soup)
And at the same time, no syntax-cleaning language extensions have been introduced (Oxygen has quite a few, as well as DWScript, which help cut drastically on the verboseness and improve expressiveness without introducing ambiguity).
Sometime ago, we were said they would be trying to close the language distance with Prism, are there still plans for that?"
(1) Post Source
"With the last iterations, I've got the feeling that Delphi code is becoming more and more unwieldy, verbose and, well, bloated.
When I say "Delphi", I mean "Delphi", other Pascal dialects have introduced more elegant forms (Prism/Oxygen especially), and have at the very least tried to fight entropy.
Just a few examples:
- anonymous methods syntax is ugly and verbose, it is very dependent on strict formatting for readability, and even then, there doesn't seem to be much in the way of standard readable formats for it), a short syntax-sugared form (as in lambdas) would help
- the newly required scoped enums for FMX result in unwieldy and hard to read code (especially when used in sets).
- unit prefixes in XE2 are unwieldy and verbose, they should have introduced Java or C#-like syntax to keep things readable, along with ability to maintain the "uses" automagically
- RTL generics classes have complicated names and still manage to be quite ambiguous (mixing types of all sort in a big naming soup)
And at the same time, no syntax-cleaning language extensions have been introduced (Oxygen has quite a few, as well as DWScript, which help cut drastically on the verboseness and improve expressiveness without introducing ambiguity).
Sometime ago, we were said they would be trying to close the language distance with Prism, are there still plans for that?"
(1) Post Source
Posts
1 comments:
>they would be trying to close the >language distance with Prism, are >there still plans for that?"
Mhhhh, but in the past also someone said EMB would focus on consistently shipping moderate improvements and manageable changes with focus on quality. One or 2 years later - 'We managed the biggest beta ever'. A solid compromise between Kylix 1 and D2005?
Land Of Confusion?
http://www.youtube.com/watch?v=zU9lv_WqK6k
Post a Comment