David Heffernan

Exit, Break and Continue are all good. No problem with them being used properly. These local variables that are shared between local functions are very different because they tend to have larger scope that is harder to manage.

I always prefer to pass parameters because it makes it much clearer what the input/output of the function is. Usually the so called convenience you refer to just leads to obfuscation.

I honestly can't make any sense of this text. Is it just me?

IDE form designer has been doing this sort of thing for over a decade with VFI

Guys, he just wants somebody to convert the code ASAP!!

This isn't the place to hire programmers is it

It seems unlikely that somebody will write your program for you. Why don't you pay a programmer to do it?

Doesn't seem like you want help. It seems like you want somebody to do it. I definitely recommend getting a programmer involved.

Maybe you need to get a programmer on your team?

Why not do this yourself? You could get some AI help to start, and then polish it up. If you want to pay somebody to do this there are plenty of online sites dedicated to facilitating that.

This looks like the tail wagging the dog.

One thing I find odd is that you feel the need to change the behaviour of basic windows API functions. Why are you doing this?

No. You detour the sysutils functions and all code in your process is impacted. Yes, detours.

This isn't going to be necessary because it will be under revision control

Is it possible that your installation has been corrupted. Why would there be Android files under Win64?

If you aren't using a swap file, where do those pages go when removed from the working set? I mean, these are pages allocated by your process. My best guess is that you did a benchmarking exercise that reached an incorrect conclusion and then you have continued using this function erroneously.

If you can do this with detours then it's preferable by far

How are you measuring the performance degradation?

Why though?

Nobody really cares that much. It's a gruesome way to go. I'd solve the problem properly but you don't want to tell us what the problem is.

So why would spending the time to do this be better than letting the system do it on demand?

This just makes your program slower though. Forcing the pages out of memory and onto disk before other programs need that memory takes time and can only lead to performance reduction. You may as well open the computer up and remove some memory sticks!

EmptyWorkingSet removes pages from the working set. Doesn't this mean your program won't be able to take advantage of memory caching?

What you seem to be in denial of is the need to recompile every rtl/vcl unit because you made a significant change to the interface of SysUtils. Are you really prepared to recompile everything? I bet there's another way to solve your problem. If only you'd tell us what the actual problem was.

You are debugging the host. You need to debug the DLL. c++ - How to debug a DLL file in Delphi - Stack Overflow