New Delphi features in Delphi 13

[mvanrijnen 130]

28 minutes ago, Uwe Raabe said:

Define big.

typical forum answer .....................................

Define, Define ?

 

 

 

something more then,

Hello World

 

 

3 million lines, 10thousand files?

 

let me rephrase ....

 

Has someone experienced progress with the code completion, lsp, codeinsight from D12.x to D13.x ?

 

 

[Steve Maughan 27]

I assume Delphi 13 can be installed alongside 12.3. Can someone confirm? If I install and it doesn't work alongside it would be a disaster for me.

 

— Steve

[pyscripter 833]

49 minutes ago, Steve Maughan said:

I assume Delphi 13 can be installed alongside 12.3. Can someone confirm?

Yes sure.  They can work side-by-side.

[Remy Lebeau 1651]

3 hours ago, Steve Maughan said:

I assume Delphi 13 can be installed alongside 12.3. Can someone confirm?

Yes. Major version releases can coexist with each other. It's minor version releases that can't.

[Attila Kovacs 683]

As with all advancing technology, some things get better and some things must get left behind. Starting with Delphi 12, the modeling features were moved to an optional add-on installation, and in Delphi 13, they're being removed entirely due to technical constraints.

https://corneliusconcepts.tech/code-formatting-delphi-13

 

ROTFL

 

One step forward, ten steps back.

 

 

 

 

 

Edited 10 hours ago by Attila Kovacs

[Uwe Raabe 2181]

9 hours ago, Attila Kovacs said:

Does the code formatter support any of the new syntaxes, or has it been removed completely? 

As part of the Modelling package it has been removed completely, too.

[Attila Kovacs 683]

47 minutes ago, Uwe Raabe said:

As part of the Modelling package it has been removed completely, too.

So no code formatting and no refactoring? Heavy.

[Perpeto 5]

5 minutes ago, Attila Kovacs said:

So no code formatting and no refactoring? Heavy.

at least we have a great working code insight left... or?

[dwrbudr 10]

No refactoring is a showstopper for me to use Delphi 13.0. Big dissapointment.

[Uwe Raabe 2181]

6 minutes ago, dwrbudr said:

No refactoring is a showstopper for me to use Delphi 13.0.

Can you say what refactoring you are actually using?

[corneliusdavid 258]

6 hours ago, Attila Kovacs said:

One step forward, ten steps back.

That's a bit of an exaggerated statement. Code formatting was an optional feature and is most useful if you've inherited old, poorly formatted code or just too lazy to indent properly in the first place (IMHO). Plus, there are other options to continue using it as expressed in the blog. I believe Embarcadero is looking to replace the feature at some point. So, to say this is a huge step back for something so minor is quite petty.

[david berneda 51]

Manual formatting for me is the best way to make sure the code is well done, calmly, as a final double-check there are no big bugs or something missing. I'd never do auto format, a headache to configure the many ways format can be done.

[Attila Kovacs 683]

1 minute ago, corneliusdavid said:

That's a bit of an exaggerated statement. Code formatting was an optional feature and is most useful if you've inherited old, poorly formatted code or just too lazy to indent properly in the first place (IMHO). Plus, there are other options to continue using it as expressed in the blog. I believe Embarcadero is looking to replace the feature at some point. So, to say this is a huge step back for something so minor is quite petty.

You are absolutely right, it's just nine steps backwards. Thank you for highlighting that.

[Attila Kovacs 683]

1 minute ago, david berneda said:

Manual formatting for me is the best way to make sure the code is well done, calmly, as a final double-check there are no big bugs or something missing. I'd never do auto format, a headache to configure the many ways format can be done.

Cool, I prefer Ctrl+D with the same settings on all PCs so versioning can work properly. Funny how opinions differ, huh?

[Uwe Raabe 2181]

I am also a Ctrl+D guy, but usually only for the current selection - and, yes, I will have also have to find a replacement, at least temporarily.

 

Currently I am inclined to use the GExperts Formatter, as it is based on the old DelForExp by Egbert van Nes, which I had been used to quite a long time in the past.

[david berneda 51]

35 minutes ago, Attila Kovacs said:

Cool, I prefer Ctrl+D with the same settings on all PCs so versioning can work properly. Funny how opinions differ, huh?

😂 I can quickly identify code not written by me when I see a minor formatting difference. Even 20 years later 😂

[dummzeuch 1696]

39 minutes ago, david berneda said:

Manual formatting for me is the best way to make sure the code is well done, calmly, as a final double-check there are no big bugs or something missing. I'd never do auto format, a headache to configure the many ways format can be done.

Autoformat has one huge advantage (apart from laziness, of course): It catches wrong indentations that suggest wrong code flows:

if Condition then
  doX;
  doY;
doOtherStuff;

 

[david berneda 51]

Ah nice catch ! I personally like to abuse of blank lines, so I quickly see the problem because after the doX; my eyes expect a blank line. Also blank line after each end; (except if the next line is also an end; )

[Anders Melander 2093]

1 hour ago, david berneda said:

Manual formatting for me is the best way to make sure the code is well done, calmly, as a final double-check there are no big bugs or something missing.

That's nice. If I send you this 800.000 line legacy project I need to clean up, when can you have it ready for me? 🙂

It was written by someone who apparently had a sporadically stuck shift key, didn't like white space, and couldn't make up his mind if 1, 2, 3, or 8 space indents were the way to go.

[Oboba 1]

13 hours ago, Steve Maughan said:

I assume Delphi 13 can be installed alongside 12.3. Can someone confirm? If I install and it doesn't work alongside it would be a disaster for me.

 

— Steve

I did it and have both versions 12.3 and 13 working.

[Oboba 1]

So the Refactor menu is greyed out, why is that? I know it didn't work properly sometimes, even basic "Rename" refactoring. I see above that it was removed with the Modelling support, then why leave the menu item greyed out and not remove it completely then?

[Patrick PREMARTIN 152]

7 hours ago, Perpeto said:

at least we have a great working code insight left... or?

As Marco Cantu pointed out, the LSP Server does not always meet expectations. They are aware of this and are working on an overhaul. In the meantime, they have reactivated the previous version of Code Insight as an option in 13 Florence.

 

Go to Tools / Options / Editor / Language / Delphi / Code audit to choose which one you want to use (in the 32 bits IDE or in the 64 bits IDE).

 

 

[Patrick PREMARTIN 152]

26 minutes ago, Oboba said:

So the Refactor menu is greyed out, why is that? I know it didn't work properly sometimes, even basic "Rename" refactoring. I see above that it was removed with the Modelling support, then why leave the menu item greyed out and not remove it completely then?

The reason is simple : it's disabled for Delphi (but can be used by IDE plugins or for next update or release), but it is used for C++Builder by Visual Assist tools.

[Attila Kovacs 683]

By the way, is the bookmarks plugin coming to 13 later?

 

[Patrick PREMARTIN 152]

2 hours ago, Uwe Raabe said:

I am also a Ctrl+D guy, but usually only for the current selection - and, yes, I will have also have to find a replacement, at least temporarily.

 

Currently I am inclined to use the GExperts Formatter, as it is based on the old DelForExp by Egbert van Nes, which I had been used to quite a long time in the past.

I've just installed the GExperts 1.3.26 available from https://blog.dummzeuch.de/2025/09/12/gexperts-1-3-26-beta-for-delphi-13/

 

It work in the 32 bits IDE and allow to enable its code formater with Ctrl+D to restore previous behavior.

 

On some of my units I see a few differences with previous default formater, but not a real problem (except for code versioning) : an indent of variables of same type declared on more than one line.

 

FField1,
FField2: integer;

 

become

 

FField1,
    FField2: integer;