David Heffernan

Yeah, I think you can ignore that answer, it's really not relevant to your question. What you are trying to do is possible by iterating over the node and its children. I would start with some code to do that iteration. Do you have such code?

I guess I misunderstood when the subject said file manifest. Details are quite important.

Why do you have a manifest file. It should be a linked resource. Delete the .manifest file.

Is that in part because of the cost of healthcare in the US?

Oh dear, I'm not having a good day. I think that obce upon a time this wasn't documented as such, and I've not kept up. But I could be wrong about that too!

Oh. Sorry. My mistake. Only in the Unicode version is an implementation detail though. I wouldn't rely on it.

I don't think that's true. You should use UniqueString. But it sounds like this isn't the cause of your problem.

The documentation says the first arg is LPCWSTR, pointer to const array. If you want to make a string writeable use UniqueString.

First argument of CreateProcess must be writeable? Is it?

The big problem here is that there is no detail. There should be a cv or a link to a linkedin profile.

No. CoInitialize doesn't report errors by throwing exceptions. You are expected to check its return value. This is stated clearly in the documentation for the function which is required reading before using it. Let's leave error handling to one side for now though. The try finally pattern is like this. res := acquireResource; try res.doSomething; finally releaseResource(res); end; The try/finally is protecting the code *between* acquisition and release. Therefore the try must be *after* acquisition.

This code is wrong. The try is always placed after the resource has been acquired.

It's broken in my view because binary search should be O(log n). And this code isn't. It isn't binary search. It's a hybrid binary and linear search. Obviously people can do what they want. I won't be using this code though.

I don't think that's right. You suggest we should just use broken code because that's likely to persuade Emba to change it? I want the program that I ship to be good.

This is why I avoid Embarcadero library code and write my own

Nobody should be calling that function that makes binary search O(n) in worst case.

Stefan is talking about a different algorithm, modified binary search algorithms know as lower or upper bound binary search. Kind of the entire point of this topic.

Wait. If you have a list with two million items that all have the same value, and you search for that value, the code will do 1 million compares to find the first item?

If there is no existing function then what? You just give up. Why is it not possible to write code?

We are talking about the bug described here https://stackoverflow.com/a/7640979/505088

No. The asker is talking about the known bug where you pass TInterfacedObject.Create to a const arg and the object is never destroyed.

This is a very long standing bug that for reasons I cannot understand Embarcadero won't fix

The asker wants to use reference counting with a mutex that is created elsewhere, and passed to the guard object. Your code does something completely different from what the asker wants to do.

Why wouldn't you do it with DDE. That's precisely what it's for.

Also the if statement is not needed and just be removed