David Heffernan

Reading Marco's article on the recently released patches for 10.4.2 I noticed this text: Is that right? If you don't keep an active update subscription, you aren't entitled to bug fixes?

The code fails to compile in XE7 with the same E2512 error. I consider a set type to be a non-nullable value type so this must be a defect.

SetWindowDisplayAffinity(Application.MainFormHandle You really need to be calling this method from CreateWnd because of VCL window recreation. Also it's kinda odd that you would use MainFormHandle from a method of the main form. Why not use Handle? But it's important to move that code to CreateWnd.

You are on subscription when 10.4.2 lands, and then the subscription expires a month later.

Neither is more suited than the other for multi-threaded programs. I don't think your usage scenario is particularly challenging or unusual as you seem to think.

You have already had numerous suggestions that meet all your requirements.

Seems like a sound idea to me

Far quicker at this point to subtract $00401000 from the address (assuming it's an exe loaded at $00400000)

This is way more complicated than you might hope. Your VCL app will run a message loop that is designed for VCL. It's not going to be able to service your FMX form. I don't expect there is a simple solution. btw, INVALID_HANDLE_VALUE is for HANDLE types, i.e. THandle in Delphi. For an invalid HWND use NULL, which is 0 in Delphi.

EurekaLog and madExcept can both do this. It's no big deal at all.

madExcept, EurekaLog, etc. are the best ways to do this. But obviously you don't have that yet, so you can just subtract $00401000 from the address and look up that value in the Publics by Value section of the map file.

Congrats to both of you

I don't get this. If you don't have any particular needs, then I don't see how anybody can offer suggestions. And if all you want is a list of libraries, then websearch will get you that. Do you know what you are going to do with these random numbers?

What properties are you looking for. The reason that there are many different algorithms in use is that different applications have different requirements.

When you buy ebooks you are granted rights to read the book, not to send to others.

Not all free. Pretty galling for any of the authors of these books to read this post.

It depends entirely on what you want to learn about.

Your way makes it impossible to pass an empty array. If an empty array is never valid, then fine. If an empty array is supported then the Pointer cast is preferable.

The reason I prefer Pointer(data) is that it doesn't trigger range check error if the array has length 0.

Start goes with finish, begin goes with end for nouns at least. For verbs start and stop are pairs.

Yeah, this is much better. And a good matching pair too.

You need to specify the calling convention, probably cdecl. And I'd declare it as PInteger and pass Pointer(data).

I think start should pair with finish, begin pairs with end, from pairs with to, etc. Don't really like start paired with end.

ofc, the naming of TrimRight is a bit of a slap in the face for Arabic speakers and other RTL languages!!! Should really be TrimEnd and TrimBeginning or something like that...

TrimRight is what you want