>Craig,
>
>>>My suggestion was not about bloat or speed. It was to make it possible to pre-process code into C++ code.
>>
>>Why? If you want C++, use C++. Am I missing something here?
>
>My idea, stated way back in this "dream" conversation, was a compile option for certain specific purposes that would limit the command set. With the elimination of macro expansion for that compile option, and addition of several other features, you might be able to build a front-end app, for example, that would pre-process into C++ code, and not require the VFP runtime.

David,

Look, if this could be done I'd be all for it. After working with the product for the period of time I have I don't think it'll happen - in this fashion.

I'm, all for your goal of making the product more flexible, faster, smaller, etc... And, if we could get it turned into a kind hybrid Foce/Clipper/Assembly/C/C++ kind of product with pre-compiler options out the proverbial wahzoo let's get it done.

Absent that I need to ask myself the question (and this is where our conversation took different paths I think), "Can I do this now, with the current set of available products?" I think we can get pretty close and as such that, in itself, obviates the need for the rewite I'd think...

Regardless, I've very much enjoyed this discussion David and I wanted to take the time to thank you for the insight you've brought to it.

Best,

DD