Der schöne Günther

What exactly is your question? You have a window handle (HWND) and you want to get the full path to the executable behind it?

I am working on a legacy project which has it enabled. I did not dare to disable it, so all new units get a compiler directive to switch full bool eval off while you have to be extra careful and always keep in mind that full boolean eval is enabled when editing "old" units. Reason? I suppose there was none and "full Boolean evaluation" sounded better than "mediocre Boolean evaluation"

It was some article that referred to a presentation from the early 90s, that's for sure. We once tried making a small application for iOS & Android, and yes, the application had so many fatal crashes with no way of debugging it that we finally gave up.

Are there more information available about the crashes themselves? And didn't Delphi get famous by demonstrating how an unhandled access violation would just produce a messagebox and continued to work afterwards instead of bringing the whole app down?

The TStringHelper was designed for immutable strings. If I'm not mistaken, Strings on platforms such as iOS are immutable whereas they are still "copy on write" on Windows. All the TStringHelper methods return a new string instance.

Why would you consider it bad? The arguments are evaluated before calling SetLength(..), so Length(..) returns the length before it was resized High(someArray) is a simple lookup, the size is known

Absolutely. Interesting and entertaining to read. Please, more of those.

I don't even want to estimate how much of my lifetime I have already spent on stuff like this. It's like the IDE does not want you to get your job done in time and is constantly putting spokes in your wheel 🤨

I always found using System.Classes.TBits easier to use than raw bit operations... if myValue.Bits[3] then (...)

Can't you just provide a simple test case with code that actually compiles, your input and your expected result?

(I am not sure if this should go to Off-Topic.) I am not sure Embarcadero intended this - The new DocWiki template for Rio has nice colours that look less depressing, but they've really overexaggerated the borders padding. Please take a look at the attached pictures for comparison. What would be the best place at Embarcadero to ask about this?

Exactly. For regular user applications, you hopefully have a global exception handler that turns an exception object into something readable for the end user. Translating computer speech to text that is shown on screen does not belong into the backend code for handling license data and whatnot.

But I don't understand - Isn't that just destructive? It throws away the additional information the default exception dialog would have shown you. It displays a generic message which is not helpful. A simple doSomething() is just better.

That's not harmful, it's just unnecessary code. What really rustles my jimmies is something like this: try doSomething(); except ShowMessage('There was an error'); end;

This is just an idea, maybe it matters whether the executable is being debugged, started from IDE or started from explorer? Maybe it inherits some settings from its parent process (the IDE).