>>I once worked for a company producing a Pascal compiler, and the procedure was this:
>>
>>1) Write the sourcecode for your new pascal compiler in ---- Pascal.
>>2) Compile your code using someone elses' Pascal compiler. This gives you a new pascal compiler.
>>3) Compile your Pascal source code with your own newly produced pascal compiler. So now you have your own product.
>>
>>I see no reason why the same shouldn't be done with C++
>
>I am currently in the process of writing a new version of VFP in- you guessed it: VFP. One of the features of my version of VFP will be the automatic generation of future versions via a 'New VFP Version Wizard'. My version of VFP will be able to propogate itself infinitely and more and more quickly only limited by the speed of the processor it is running on, or until the VFP version number grows too large for available storage space. Early testing of my product has quickly taken me to versions as high as VFP 10^32.
>
>That particular version has a really advanced object model, and is the first version to actually recognize programmer feelings and emotions, and translate them into wonderful software via intuitive (really intuitive) wizards and builders. In addition to all this, it runs on Windows CE and Linux.
>
>I will post my VFP version here in the files section as soon as I am finished with it.

Great,

I hear the MS are testing a similar thing with a VB version wizard. Unfortunately, because of serious inheritance problems, all they can get it to produce is GW Basic V.1