Hi Michael,

My English post was certainly not idiomatic English. So this pos was some French prose for Thierry to grasp... I was indeed just kidding on the fact I stopped coding C and run machine-object code-making in 1993 (or 1994) and that I'd be glad not to get into that old loop in 2017. The work by Chuanbing is most certainly wonderful. But I just try to avoid resort compiler technology when I can avoid it.

I belong to the foxpro early adopters list, say around 1986 if I can remember well. I admit that I never touched a compiler during over 23 years (yes that a period of time after which you are allowed to forget the stuff) and I am not really keen to move into compiler technology and re-learn it again.

Grasping the subtleties of compile/link and and other stuff is possibly a joy for linux eyes. I can understand that very we. But in my old eyes, this has a taste of clipper (yes a couple of months during the eighties). The documentation for this new set of tools is a bit too low-level-orientated for my taste.

I am just lost at what I read on this possibly great set of tools. As most of us here, I run an over 100-K lines compact and complex code base. Moving stuff means a lot more than a build process!

A robust feedback on what can achieved with Chuanbing Chen work - outside the plain and obvious code protection of course - would be helpful. Code support level, performance, memory occupation, robustness, startup time, ocx and com-based automation support. A pragmatic "I used it this way and it worked for me".

Thanks for your reading

Daniel