David Heffernan

For the sake of future readers, this example is not minimal. I can't imagine where there are two goto statements. The issue you raise needs one. Minimality is important. This is the example you should have posted: procedure Foo; label L1; begin try goto L1; finally end; L1:// E2127 here end; The other thing that is missing is what the compiler error says. Often there's information there. Why omit it. Again for future readers, it says:

It's a mutex. One thread at a time through protected blocks. Is it the right structure? Maybe. But using a mutex is only going to be useful if you do it right. Do you see the code that accesses FOperationsLoaded outside the mutex. What's your rationale there? Anyway it's kinda hard to analyse your code with it spread over loads of different posts.

I wrote my own set of collections years ago to escape from the bugs in the RTL collections, but I suspect there aren't so many these days

waiting for @Stefan Glienke to show up and answer this

Owns values, means "collection is going to call free on every vamue when it is no longer held in the list". Which implies it needs to be an instance of a class. A record is not.

Just as a general piece of advice, when new Delphi versions are released, you'd normally expect to go to the repo for latest source to work with that version. Getting used to using repos rather than relying on and waiting for packaged releases is a skill worth learning.

If the methods here can all be called arbitrarily from multiple threads then you seem to have at the very least a race on FOperationsLoaded. I don't understand what that call to Wait is for either.

It's one of my goals to release a version 13 of my software, which is currently at 11.4. I'd be able to retire then!!

You can use QualityPortal to find info about bugs being fixed

If this isn't about security then there's no need for the feature you are trying to implement.

It does indeed. But I do find it a little hard to get excited by festures that other tools have had for years.

It's presumably a small overhead at process creation

And makes your app a target for anti virus products. And what what gain? You end up with the same executable loaded in memory. I've never understood the point of this tool.

I'm pretty sure that you can have all of those things in the same language

You could find the answer for this quote readily by doing some research. Have you looked?

I don't understand this sentence. Read the map file. This hasn't bothered you before, why do you suddenly need to reason about this now. What are these effects you talk about? Anyway, you measured the size of your executables, but now you claim that performance is what concerns. If performance concerns you I recommend that you measure performance. Seems like you've measured the wrong thing. Anyway, if you really care about performance you'd surely not be using delphi, literally the worst compiler for performance.

Why do you care about these tiny differences in these tiny executables? If you care use Delphi 5.

All these marketing people trying to generate buzz around a name. How about fixing the bugs and making the product better? Then you can call it anything you like and it will sell.

There's a what's new that you can read, and there's not much there in my opinion.

The fix the actual problem. Otherwise your security is broken.

I don't think this is possible because there's no good use for such a feature

Really not enticing me to click on this link by posting in a huge font with no summary or commentary.

This sounds like a really interesting numerical problem! I suspect that in practical terms, sorting is going to be the winner though.

https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Declared_Constants It's all in here

I'm quite excited about escaping GIL tyrrany but shared global state in the python extension module I develop is going to be tricky. I'm looking forward to seeing what you've done here and drawing some inspiration!!