David Heffernan

I don't think that's the case. If you need to interface with a C++ codebase, then you need to create either a C wrapper, or a COM wrapper, but in each case you aren't limited to C++Builder. Whichever compiler you use to compile the C++, you compile the C wrapper, or the COM wrapper. The point is that the C or COM wrappers are compiler agnostic. But C++ code is, in general, not compiler agnostic. So you just need to compile your wrapper in the same toolchain as the C++ library. There are actually tools to create such wrappers. I'm thinking of SWIG. But there's no way that there's going to be a Delphi produced which can consume C++ libraries compiled by some arbitrary C++ compiler.

Because Delphi 1 could import functions from DLLs.

That's inevitable though isn't it. Because OpenCV is written in C++. For which there is no single binary interface.

This can already be done, and has been possible since Delphi 1

How much are you prepared to pay? What exactly does the job entail? You may be better asking directly on sites that are designed to put together people looking for contract programmers. Are you asking any more than you did here:

It's not safer than C++, it's exactly the same as C++

This is so stupid. Delphi and C++ are exactly the same in this regard.

In 2147 people will still be suggesting setting DoubleBuffered true to solve flicker problems rather than fixing the actual problem

Title bar panel is effectively VCL styles because theres no api for that, I think. So you probably just have to suck it up.

Late information boo

You should report these as bugs to Embarcadero, but unfortunately they've been unable to provide a mechanism for reporting bugs for last past few months.

I guess ARC per-se wasn't the big problem, it was more the attempt to support ARC compilers and non-ARC compilers with the same codebases??

Yes.

Wrong. Setting a dynamic array to nil is identical to setting length to 0 and identical to passing it to Finalize.

That doesn't help if you have multiple variables that refer to the same instance which I guess is a more likely scenario for double free.

This sounds completely broken. What if the file starts with the sentinel value that indicates that you have a utf8 payload. Why aren't you passing a separate header, and then the payload? And why are you passing utf16 at all. Isn't that just expensive. And if you must pass around utf16 please tell me that you are handling byte order correctly.

What's pretty astonishing is that the NSA thinks that Delphi is memory safe! See White House urges developers to avoid C and C++, use 'memory-safe' programming languages | Tom's Hardware (tomshardware.com) I guess the NSA don't know anything about Delphi. obj := TObject.Create; obj.Free; obj.Free; Take that, NSA!

Just let me know what you can do with C++ that you can't do with Delphi, in terms of safety

No it's not. Not really the point if a government agency will only accept work using tools that meet certain criterion. You can either follow the specification and have a chance of getting the work. Or argue about the specification and be completely ignored. That's just reality.

Not according to Embarcadero. According to Embarcadero Delphi is blazing fast because it uses native code. We all know that to be absolute marketing BS and in fact Delphi compilers produce shitty code that often runs very slowly. Yes, my original post was sarcasm.

Delphi produces native code, and therefore is fast

That's not my example. Nobody wants to do this with a value type because it's a non terminating recursion. Have a look at my example code to see what I'm actually talking about.

None of that applies to my example above.

I don't really follow this. If you have to modify your code to add the message dialog, before you start debugging, then I'm not quite sure why you can't run with a debugger attached. If you are happy to attach the debugger later, why can't you attach it at the start?

This isn't really a great example. The sort of thing that I want to do with records, but cannot, is this: type A = record; B = record; A = record function foo: B; end; B = record function bar: A; end; I can get round this using helpers right now, but I don't understand why I can't do this directly as above.