Thanks for the response, Alan.

Went looking at blogs and videos about VBx, Silverlight, etc. Wow, a lot is coming up. Try hard to keep a coherent story. I say that because in the past VB seems to have asked developers to change their approach every so often. One of the admirable things about VFP (after introduction of objects in VFP 3) was that it evolved without jumping all over the place, keeping backward compatibility so you could use the old while absorbing the new. Being able to use your old code and knowledge is very important, otherwise you are on a treadmill.

Another thing, please let LINQ directly access and create free DBF tables. They are very useful Alan. Eventually create a new iteration of free tables: 64 bits, with somewhat longer column names.

Thanks, Alex

>It means improvements to its existing dynamic capabilities and integration with the other dynamic languages (like VB and C# share on the CLR). So VB will handle both CLR and DLR capabilities. If you look at Craig's blog, he also comments on the REPL capability that Paul Vick blogged about - otherwise known as a command window.
>
>yag
>
>>I see that VB will be based in the DLR (Dynamic CLR). What implication does this have, exactly?
>>
>>http://blogs.msdn.com/hugunin/archive/2007/04/30/a-dynamic-language-runtime-dlr.aspx
>>
>>

>>We're initially building four languages on top of the DLR - Python, JavaScript (EcmaScript 3.0), Visual Basic and Ruby.
>>We shipped today both Python and JavaScript as part of the Silverlight 1.1alpha1 release today. John Lam and I will be
>>demoing all four languages, including VB and Ruby, working together during our talk tomorrow at 11:45.
>>

>>
>>TIA,
>>
>>Alex