Mark NZ

Find declaration only ever worked for us in any Delphi version for trivial projects

I presume he means the problem we see with standard scrolling in Delphi 13 where you're scrolling down through a file and it stops scrolling until you get to where you intend to stop. It's happened lots here but I just went to reproduce to include steps and it didn't do it! Anyway, it's much better than the previous behaviour where you'd be scrolling (usually with mouse wheel) and the IDE would continue scrolling, for seconds, sometimes many, after you stopped turning the wheel. I think this was related to running on a HighDPI screen.

Sometime developers/companies have to wait for the official release so that they can update their third party dependencies before they can build and internally test their own components. We don't do components but still have to wait for official releases and then for Report Builder to update to be able to build one of our projects, even though we have Report Builder source - and that's because Report Builder source doesn't include all source files, there's several dcu's in there that we use that are a problem when the Delphi version changes. It'd also be helpful if library/component writers stopped using lots of the awful single version defines and instead used {$if CompilerVersion > 27} to make running new IDE versions simpler, although I suspect that might not be supported in very old Delphi's😞

Is NameOf(T) really that much use on it's own? Unless I missed something you still can't get NameOf current method or source file or LineOf/CurrentLine. I would have thought they would have been trivial to add at the same time with minimal extra testing.

The refactoring removal is actually the biggest benefit of Dephi 13.0 for me so far. It only ever worked on a trivially small project and on our large projects just moving the mouse past the menu option not fast enough caused minute+ freezes, that was VERY frustrating for me when debugging and trying to jump to statement.

Yup, LSP still crashes frequently. Possibly works a bit better before it crashes.

I've tried this with AV tools a couple of times in the past, it was a waste of time, Embarcadero wasn't interested.

For Delphi they have issues at times (frequently for us) when docked 😞

You'll also get emails when the issue is changed/updated. In my experience from trawling issues and the handful I've raised it seems relatively rare for an issue to be worked on or fixed.

The uninitialized values of b & c are not surprising, they'll potentially just be what was last in memory at the address that's being used for them. Regarding what the debugger is showing, we regularly get the same/similar behaviour in Delphi for inline variables (wrong values or unable to display) and at times rubbish values for normal local variables as well 😞

Yep, sometimes they just close as cannot reproduce and occasionally something actually happens. I raised an issue with a few days ago with 12.3 AV's occurring when swapping between RDP/local that happens often but I don't have steps to be able to do it on demand, have previously logged or commented on a similar problem with info that I suspect it's related to resolution or dpi changing during the connection process. Created the issue as I had a call stack which could be of help for diagnosis, adding extra logging etc. I don't normally bother with logging issues as Embarcadero quality, support and fixes are so poor (and that's me being generous, internally I swear about the product and the support)

Once it's opened be prepared for multi year waits 😞

For us many features (including those 2) are broken or work poorly in many recent versions of Delphi (10.x onwards?) when working in large projects, still so in Delphi 12.3

They added LSP logging which could be turned on for tracking down bugs they couldn't reproduce (similar to what we do at times for knarly customer bugs that we can't reproduce), turned it on, gave them the logs, from memory no related fixes were forthcoming. I've also looked at their general source base (eg VCL) given them the bug and the fix and not had them actioned 😞

They say that but in my opinion it doesn't appear to have good practical results, yes they do have fixes but there are LOTS of outstanding issues that really annoy people and the bugs have been increasing at a substantially faster rate than are fixed for many years- it was really telling viewing the raised vs resolved Jira graphs on the old quality portal. It was also pretty bad seeing the number of "resolved/fixed" bugs that were simply closed because Embarcadero couldn't reproduce while customers were still reporting they were a problem. Additionally a number of their "fixes" don't properly fix the problem or introduce new bugs. From the outside it appears like they don't have much in the way of development resources, especially experienced ones that know the code really well.