Not exactly my point. Languages are structures and constructs, functions and commands. VB and C# are very different in this already.

But my point is if there are features added that provide some new functionality - I heavily favor .Net SDK integration over mucking with the languages.

Think about it - when you write .Net code, what do you really do with the language itself??? Not that much but do assignments, looping strucutres, arithmetic etc. The rest is all done with the SDK. String manipulation, data access, XML, net access - all SDK.

There are a few things I can see as useful - like integration of a data language that makes it easier to write SQL code - like VFP. Seeing that Yag is involved I wouldn't be surprised to see this as a new feature of VB possibly which would be nice. But it still wouldn't make me want to use it either <bg>...


+++ Rick ---

>>But there's internal competition and pride driving that at Microsoft more likely than what's best for customers <g>...
>
>I think you have to look at the alternatives before you can admit that this is a bad thing. What would be advantage of the CLR over its competitors if it supported two languages (ignoring the other umpteen+ it really supports) where the only difference between them were simple syntax things?
>
>But what does worry me is if a feature is added to VB.NET and in the next rev, C# gets it, if they are different implementations they might be in subtle, and annoying ways.