David Heffernan

What should happen here

I don't really know. There's a part of me that says C++ because I know I'll have good compilers forever. But porting would be hard. For instance, we use lots of nested functions, which don't exist in C++. Not sure how we'd handle that. I think there'd need to be a lot of refactoring of the code in Delphi first to enable a semi automated translation.

I don't care that much about the IDE. It's the compiler and the language that matters more to me.

Your specification in the original post is incomplete so it's not surprising that people don't know what you want. Your clarification is still unclear. Until you can define precisely what you want the code to do how could you expect anyone, even yourself, to be able to write it.

All kinda moot since you'd never use set membership rather than InRange

No, your way is sure to work. Crack on.

Yeah, pretty sure that's all that's needed. Can't believe nobody thought of that before.

What do you mean by "shortest"?

But that's not what it is. It's Delphi 12. Like last time it was Delphi 11 and then 11.1 and then 11.2. So maybe the next one after 12 will be 12.1. Or maybe it will be 13. Or maybe 14. The fact that so many people have such problems with knowing the versions is a sign that their policy is poor. I'm expecting to hear about XE12 before long.

Would you like a pony with that too? Honestly, the entitlement of that statement!

Wouldn't you just write an exhaustive unit test that ensured nothing could go wrong

To search out bad luck amongst our Japanese markets??

None of us can do this though. Why are you posting here instead of submitting a QP request? We aren't the people you need to convince.

Why are you arguing. Surely you have an actual problem to solve. Why don't you just do that. You know all you need to know now.

Well, you say that, but it's the placement of the label that determines whether this an error or not so I think that's fine.

Actually that's not where the compiler reports the error. The compiler reports the error as indicated in my post. At the label.

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