David Heffernan

What I can't understand is why you would ever need to call such a function. Broadly, you never ask if a file is in use an any one moment. You try to do something with a file, and then handle the scenario that it fails due to being open.

That doesn't make a lot of sense. What is the successor of a collection. Perhaps you mean the successor of a member of a collection. But that only makes sense in the context of the collection.

For an array indexed access is usually fastest. Delphi RTL enumerators are often sub optimal. I mean, heap allocation to iterate a collection ffs.

> Is a standard comment before each procedure implementation useful? No

High is fine for an array. Pred is a stupid way to write Count - 1. I mean, you aren't proposing writing Pred(Length(arr)) are you.

No. It's pointless verbiage. Use List.Count - 1

The difference is that Pred(...) is verbose and opaque.

That's true type not open type

Find a C API and convert the header file.

I think it has a name something like &op_Equality. You should be able to enumerate the methods of the type.

If that code would compile, then there wouldn't be much point in having the library. Think about what the literal on the rhs of the assignment actually is.

I doubt anyone wants to download your software. I know I don't. Normally if you want help you'd explain more what the problem is. Anyway, never mind.

I'm afraid that none of this makes a lot of sense. Why do you feel that there should only be one explorer process? Why does that matter?

It's common to have lots of explorer processes. There's an option that means each window is run from a different process. I can't understand why you would feel that there should only be a single explorer process. That's for the system to decide. If you want to interact with the system then you need to follow its rules. You don't make the system rules.

Of course not. You aren't generating the html.

How are you generating the original html?

Yes, if it is an affinity mask then it should be NativeUInt.

Sounds like the classic OOP trap of trying to solve all problems with inheritance. Good OOP programmers hardly ever use inheritance to solve problems.

I mean that this thing is named as though it is an affinity mask. And on Windows that makes it pointer sized. So, NativeUInt.

Affinity masks for pointer sized.

Don't try to use more than 48 threads in that case

If the hacker gets the program, and there is a hard coded key in the program, then it's trivial to hack.

Is it 96 cpus, or 48 with 2 threads per core? Is the memory NUMA?

What do you think this does?

Seems like it's not really worthwhile then....