> > 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.
No, you are right. This issue won't render VB.NET unusable for beginners. There are a whole host of other issues which already fill that void. Patrick Burrows With a horrid little pistol and a lariat -------------------- Now Playing: mighty mighty bosstones - track 12 - -------------------- You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
