> 1 - What's new is that the behaviour is different to VB6. OK, the specific issue is, but the broader issue of implicit conversion subtleties, especially with dates, is not new at all. Although different, I think VB.NET's (and the CLR's) tighter type enforcement will prevent more bugs than it causes. As you correctly state, this is only a problem for experienced VB developers who are used to doing things a certain way. Mark was saying, in so many words, that this would cause problems that would render VB no longer suitable for beginners and that this was a reason for rejecting VB.NET. I think that's unhelpful and, truthfully, a ridiculous reaction to a very minor issue.
BTW, I'm not a VB lover or a MS lover who just can't stand to see them criticized. I use several languages and appreciate the benefits of each. What I can't stand is a post to a technical forum that offers only bashing of the very technology the forum represents. -- Steve Johnson 3t Systems You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
