>>> LOL, anything with 'c++ inlined' is probably anything BUT secure :-) So many ways to shoot yourself in the foot with C/C++ and memory management.
>

Er - you're not going to inline a commercial library. And even if you 'just' call it you still have to deal with memory management buffer overruns and all sorts of other security issues that make it very easy to do damage.

But whatever floats your boat - if you're into that sort of pain by all means - somebody's gotta do it :-) I've done my share of C++ over the years and I'd be happy if I NEVER have to look at it ever again.

+++ Rick ---

>Not really- neophytes might struggle to cut on the dotted line but ASM or C++ (for example) out of the 7z repository is commercial grade, documented and designed for this purpose. Interleaving with VFP means that even the best Journeyman olydbg jockeys in the world will be given pause. At the moment we're routinely interleaving ASM that works flawlessly except when a Windows patch broke one of our debugger checks(!)
>
>FWIW: the latest VFP Compiler offers 64-bit C++ exe and dll compiled from an ordinary VFP project. Experimenting so far = working well unless you've used 32-bit dlls/flls or ActiveX, and of course there aren't so many hacker olydbg equivalents for 64-bit yet. So far my take is that the 64bit version is for scaling server apps but for user apps the 32-bit versions work beautifully on everything up to Windows 10 and you get to use all the VFPX UI features.
>
>Also btw, wanted to thank you for your blog about IE versions in the Web Control. Phew- we were having to consider Chrome and other addons that broke the ease of deployment that remains such a breath of fresh air with stuff written over the decades in VFP.