Excuse me???

Often requested to drop macro substitution? Sorry, I don't beleive that for one moment. Rather, folks don't want to give up macro substitution. This issue comes up when folks want VFP to be compiled - like VB. This would mean the giving up of macro substituion. Folks usually back off when they have make this compromise.

Sorry Craig, but you are flat out incorrect here.... Again, you have pulled out "facts" from think air...< s >...


>>Dear all,
>>
>>Now that the .Net dust has settled a bit, we know that VFP is not going to be able to run on top of CLR. I was thinking that maybe that MS could just strip out support for macro subsitution from VFP. Since the release of Visual .Net is still at lease 6 months out some work can still be done. Other languages like cobol, Effiel and others are going to support CLR why not VFP? I can live without Macro subsitution if that is in the way of CLR support. Does anyone support my idea? Thanks.
>>
>>Regards,
>>Kueh.
>
>It is often requested to drop macro substitution. You won't gain much. There are many other areas I'd rather see the Fox team work on before attempting to remove macro substitution.