I actually do code .Net code in Notepad so I know what you're talking about. And I must say that it's VB developers who are capable of creating code that's completely unreadable. Take case sensitivity for example - most VB developers love the fact that they don't have to be bothered with such things as consistently casing their identifiers. In their words it's a productivity issue, you don't have to think about which letter to capitalize. Most of the other issues I had (not requiring variable declarations, using On Error and so on) are being fixed with VB.Net but it's still a language designed for people who prefer to code with their mouse. They don't care what the actual code is, they wouldn't understand it anyways. And since it does seems that most programmers these days are like this, they do not take the time to actually understand what they're doing, I'm pretty secure about my future, there's going to be tons and tons of projects that need to be redone because some VB idiot botched them.
Remember we talked about having Ivrit Mivnit compile as a CLI language? ;)
I was looking for you too, but you didn't show up... I guess we were always in different tracks.
You write in your post:
"the class does both interface inheritance and implementation inheritance". I guess what you mean is that a class can inherit interface implementation, and can inherit its ancestor functionality. However, I think that in order to make a clear distinction between interface implementation and class inheritance, the term "implementation" should be used only when talking about interfaces, and not classes.
BTW - what's going on with the TDD seminar? I'm looking for that eagerly!
Memi: I was actually referring to "implemkentation Inheritance" as the *real* inheritance as in that the class inherits implementation details, not just just the interface.
As for the TDD workshop: should be next weel see my blog for more details on that.