I´m addressing this to you personally and hope it doesn´t get ignored again. Saw replies to the 'Try and Catch' thread today. Rather know it´s a stupid idea than running against this wall.

Anders Hejlsberg: "LINQ allows query expressions to benefit from ... compile-time syntax checking, static typing and IntelliSense that was previously available only to imperative code."

Curiosity almost killed me when they first talked about the Fox in VB some weeks ago. While I´m still trying to partially understand the code, there is a Sedna idea:

*************************
Could you enhance Intellisense that it kicks in if one uses square brackets instead of double quotes for query expressions,...?
*************************

My idea actually originates from the constant values in VFP being filled in at precompile time when using square brackets instead of other delimiters (single / double quotes).

#DEFINE wdthxrnr 3
*index expression
gaCdxX(1,1)=[CHARFIELD+STR(INTFIELD,wdthxrnr)]

*results in
gaCdxX(1,1)=[CHARFIELD+STR(INTFIELD,3)]
*at compile time

*******************
Wouldn´t it be a very straightforward enhancement if the square brackets would not only be 'transparent' for pre-compile, but for syntax-checking and Intellisense too?
*******************

BTW: I´d *never ever* found this little gem in the docs / nowadays if I hadn´t known it for ten years or more.

And: I´d *never ever* comprehend the difference between Evaluate() and macro substitution from the docs if I wouldn´t already know.

And: Comments would be greatly appreciated. Still waiting for ALocks() comments and a working Isolated VFP COM object in a .Net app.

Thanks
G