>Thanks. Let's stick with the examples. There is a lot of FUD about COM and VFP out there that is hard (as you can see ) to get rid of.
>VFP has a way forward IMO and that way is to emulate PHP but:

Until windows no longer will run 32 bit programs.

>1.) perform better because: it has an ISAPI module (much better than fastCGI)

Except PHP was designed to run on Lynix and apachee so that comparison does not wash.

>2.) can take advantage of multi-core processors

VFP is not multi-threaded. The multi-threading comes from the browser launching a thread of VFP as needed. PHP works the same way.

>3.) has true multi-threading
>4.) has a built-in integrated database and its own unique features
>
>btw, wwc is COM too - the slow, non multi-threaded EXE kind unless the dog slow and unscalable File Mode is used..
>
>>>Here is a good place to start. http://us2.php.net/manual/en/book.strings.php
>
>this is nice.
>
> $ntimes = 4;
> $descrp = "I have use this function {$ntimes} this week";
> $descrp = 'I have use this function '.$ntimes. 'this week';
>
>
>I have mainly used WW so I don't know much about ActiveVFP but ActiveVFP is COM and COM has a lot of overhead in it self. The big difference is PHP has a way forward VFP does not.
>
>I just remembered. Thanks to the Facebook people, PHP can now be compiled and run as compiled code instead of an interpreter.