>I believe that it would be very powerful for VFP to support some limited capabilities for compilation into native code. This would be particularly helpful when you need to perform some numerically intensive operations in an iterative fashion, as doing this with VFP's variant data types under interpreted code is very slow. This capability could be implemented in a very constrained way and yet still be very useful. For example, it could be implemented such that native compilation must be performed on an entire procedure, the procedure would only support a subset of the language syntax, and would not allow macro substitution. Compilation would produce a DLL-like entity that would be linked into your application when the app is built or could be loaded and called during app development. Once the call is made to the procedure, all execution would be via native code rather than interpreted code. This would be a great way to support numerically intensive components of an application
>without needing to write DLL's in (for example) VC++.

I would have to agree with you. Even VB still supports the ability to compile to p-code for those who choose to do so. Why not have a debug version and a final version as in VC++? I don't care how much memory or how fast the processor, for everyone has a need for speed... :)

Jack Mendenhall
RMI