New Delphi features in Delphi 13

[Patrick PREMARTIN 152]

5 minutes ago, Attila Kovacs said:

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

 

Bookmarks, Navigator and the multi threading debugger extension from Parnassus should arrive on GetIt in a few days.

[Anders Melander 2096]

1 hour ago, Patrick PREMARTIN said:

The reason is simple : it's disabled for Delphi (but can be used by IDE plugins or for next update or release)

It should have been hidden for Delphi. Having it visible but but disabled, with no way to make it enabled, is just confusing; Poor UI design.

https://learn.microsoft.com/en-us/windows/win32/uxguide/win-dialog-box#disabling-or-removing-controls-vs-giving-error-messages

[David Heffernan 2472]

7 hours ago, dummzeuch said:

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;

 

I mean just never ever ever use single statement, always use compound and it's a non problem. 

[Mark- 37]

10 hours ago, david berneda said:

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

Ditto. I was deposed years ago and the attorney was asking me questions about the code. He had a printout. He got to one part and I said that is not mine. He asked how did I know. I showed him all the code that was mine by the style of formatting I use. That ended the code questions.

 

[Attila Kovacs 683]

5 hours ago, Mark- said:

Ditto. I was deposed years ago and the attorney was asking me questions about the code. He had a printout. He got to one part and I said that is not mine. He asked how did I know. I showed him all the code that was mine by the style of formatting I use. That ended the code questions.

 

versioning/blame 🙂

[Lars Fosdal 1904]

I spent nearly a decade undoing my built-in left-pinky-shift uppercase reserved word habit, imbued during the pre-syntax-coloring years 🤣

 

However, I won't give up my if/then/else formatting, and I haven't found a formatter able to replicate it. So, I guess I don't miss that formatter.

[dummzeuch 1701]

8 hours ago, David Heffernan said:

I mean just never ever ever use single statement, always use compound and it's a non problem. 

So if you get some source code to work on, you really go through it and add begin/end for every code block? I for one are definitely to lazy for that.

[dummzeuch 1701]

32 minutes ago, Lars Fosdal said:

🤣

However, I won't give up my if/then/else formatting, and I haven't found a formatter able to replicate it.

What kind of strange formatting might that be?

[Uwe Raabe 2187]

40 minutes ago, dummzeuch said:

What kind of strange formatting might that be?

I was just about asking the same 

[Dalija Prasnikar 1533]

1 hour ago, dummzeuch said:

So if you get some source code to work on, you really go through it and add begin/end for every code block? I for one are definitely to lazy for that.

And then you write things like this https://quality.embarcadero.com/browse/RSP-23924

 

function TBaseFoo.BrokenFoo: IFoo;
var
  LOwner: TComponent;
begin
  Result := nil;
  if Supports(Self, IFoo) then
    Result := Self as IFoo
  else
    LOwner := Owner;
    // if block execution will continue here !!!! 
    while LOwner <> nil do
    begin
      if Supports(LOwner, IFoo) then
      begin
        Result := LOwner as IFoo;
        Break;
      end
      else
        LOwner := LOwner.Owner;
    end;
end;

 

Edited 2 hours ago by Dalija Prasnikar

[David Heffernan 2472]

4 hours ago, dummzeuch said:

So if you get some source code to work on, you really go through it and add begin/end for every code block? I for one are definitely to lazy for that.

I don't "get some source code to work on". It's all our own code and we all follow the house style, obviously.