David Heffernan

Not sure it's relevant but that x64 should use .PUSHNV to preserve rbx. And I think that also makes .NOFRAME incorrect.

The FMX bitmap that you save is a compressed bitmap. The VCL bitmap is a Windows bitmap, uncompressed.

I don't think that mixing VCL and FMX will work. So I'd just rule that out.

Wouldn't it just be easier to detect the webcam without trying to mix FMX into the system?

With over a million lines of code, it's an epic task to migrate. I can't believe that the increase in compiler time would be significant.

C# compilation is pretty darn fast. Delphi compilation for 64 bit on Windows is not exactly fast. I'm sure that a first pass to define record type layouts followed by a second pass for everything else would not be costly. This isn't going to be about compilation speedy. It's about the pain of refactoring the front end.

It is possible. Plenty of languages can handle this. Emba could implement it if they chose to.

Well no, of course not. So we are stuck with this second rate language.

The argument is that its a single pass compile. So make it two pass. Simples.

You should be able to forward declare their methods. No reason not to be able to do that.

Bloody annoying that this can't be done

I personally don't think you can do better than helpers. That's what I do.

You think wrong

Find out by debugging. Set a breakpoint on SetLastError. And inspect the call stack when it triggers.

The only error here is the code that calls GetLastError and uses the value at a time when its return value is meaningless. All you have to do is to stop doing that.

Yeah, should be using '%p' format string

Sure. But so what?

Amazing that they can't produce a 64 bit IDE....

Don't think of the problem as how to write the code effectively given the data structure. Think of the problem as choosing a combination of data structure and algorithm to solve your problem. In other words, ask about the underlying problem, and be prepared to consider a variety of other data structures, which in concert with the right algorithm might perform best.

8 times faster sounds amazing, if the only thing you ever do is call Pos on data that is already in the cache. I'll bet that for a lot of real world applications you wouldn't see any benefit.

Cross posted: https://stackoverflow.com/questions/61656924/smartpointers-do-not-work-well-with-a-generic-tobjectlist-in-delphi

If possible you should use side by side assemblies

Those links are to Stefan's clone. What about the author's repo?

Do you have any particular reason to believe that XE is a supported compiler?

Why do you feel that there might be a problem? The rules for identifiers are well documented. These all meet the rules.