>Michel,
>
>>>Xbase treats & macros and VFP treats && comment tokens higher in the parsing precedence than they should. It's one thing about Xbase that has really irked me for a long time that string constants can get mangled because of this.
>>
>>Thanks for the explanation, I'll submit a request for enhancement in the product for that.
>
>You can suggest the ER and I agree with you, but it's likely that this functionality will never be changed for backwards compatibility issues so don't get your hopes up that it'll get fixed.

I wonder how improving this to work as expected can harm backward compatibility?

I mean you simply cannot code && ANYWHERE except as a comment now, as anywhere ELSE givces an error message. So if it is changed to work as one might hope (not give error messages) in sensible places other than comments there should be no backward compatibility issue on this.

Am I missing saomething?