David,
I belive that '&&' goes back to the dbase II. Anyway, I tested it in Fox 2.6a before posting and there's excerpt from FoxPro 2.6 help
Indicate the beginning of a non-executing comment line in a program file.
Syntax
or
or
>Sergey,
>
>I don't think we got && end of line comments until VFP3.
>
>Before that the parser simply ignored the line content once a fully parseable line was read. Which led to (junk IMHO) code like this:
>
>
if ( cond )
> ...
>endif cond
>
>>It's a known issue since FOX 2.6 days, maybe even eirlier. FoxPro incorrectly treat '&&' in the string literal as beginning of the inline comment. A workaround is to separeate '&&' characters.
lcTxt= "&" + "&"
>>lcTxt = "!!!#&" + "&"
>>and so on
--sb--
