Hi, Neil.

>As there has been quite a lengthy thread on optimisations and speed the following is a snippet from the new C++ compiler features in the Whidbey release.
>
>"Furthermore, the Visual C++ Whidbey compiler will be able to optimize MSIL beyond what is possible with other managed languages."
>
>"One of many enhancements planned for the C++ compiler in Whidbey is Profile Guided Optimizations (POGO). POGO technology enables the compiler to instrument an application and collect information on how the application is used at runtime. This information enables Visual C++ to further optimize generated code based on real-world application usage patterns."
>
>http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx
>
>I am sure you will agree that this is pretty cool and if the VFP team read this my no. 1 wish list item is now as follows.
>
>1] Can you stick POGO into our compiler? <vbg>

It would be nice, but I don't think this kind of technology doesn't apply to VFP. This is a trick you can do on a very low-level compiler. VFP compiler just generates p-code that is later interpreted by the runtime. I don't think there is too much room for p-code optimization.

For an interpreter, VFP is already quite fast, anyway.

See you,