>I could be wrong, but I seem to recall that the C# team originally wanted to go some completely different route than what LINQ is...the phrase "relational operators" comes to mind.
>
>Perhaps what MSR was working on was what C# was eyeing initially. But I think it was different than what LINQ became.

Hi, John.

C Omega is a mix of several previous project around programming extensions for C#, joined about 2004 under one umbrella. The projects included query constructs, relational data extensions, Xml manipulation (previously Xen or X#) and concurreny handling (Polyphonic C#).

I did presentations about this topics around 2005 and what later became DLINQ (or LINQ to SQL) was pretty much the same, with some minor adjustments, full IDE support, etc. By the way, C Omega keeps going on as parts of it, like the concurreny management has not yet made its way into the mainstream language.

While it seems logical that some of the VFP team developers could have contributed to the final implementation, I really doubt they played an important role in the design. Of course, the xBase notion of integrating queries into the language is something that most of the people doing this surely had in mind, but the conceptual background and the final implementation greatly differs from what we have VFP.

Just have in mind that the whole SQL-like syntax is an afterthought. The real syntax behind the scenes (which you actually can use, of course) is something completely based on methods, like:

var query = 
   developers
       .Where(d => d.team == "VFP"
       .Select(d => new { 
                      FullName = d.FirstName + " " + d.LastName, 
                      Role = d.Role });

I'm sorry to come against your statement, but I guess what you said, coming from someone who worked at the VFP team, will be taken as an absolute truth from the community, and I guess whether you are totally sure about that or is it a personal opinion based on what you see around, which can be an interpretation.

Best regards,