RBerenguel wrote:SmoothOper wrote:quantumf wrote:As VB.NET is equivalent to c# in essentially every way, it's clearly an object oriented language by design. It has the flavour of basic, with it's terms and symbols, and in a concession to VB6 programmers, it allows a procedural, non-OO form. I have developed multiple large (object oriented) systems with VB.NET, and find it a perfectly comfortable OO language
On error resume next
On erro goto....
Clearly not OO or easy to manage in large projects. I find these constructs especially discomforting, and especially error prone, for anything but the simplest of code. Not to mention, that sooner or later in large projects you have to do an N^2 or N*log(n) operation like sorts or searches, then it pretty much crawls to a halt. Furthermore, VB programmers like many single language programmers fail to recognize the relative disadvantages of their language, and are generally thin skinned and uncool about it. After all if it were object oriented then they shouldn't feel that it is too difficult to use another language in the first place, but again this is not the case.
Like object-orientedness was the panacea to solve everything. Lisp programmers are pretty much happy without ever resorting to CLOS. Go has interfaces and structs and it works pretty well. The example above? This is error handling. Error handling is good, and there's no need to add object-mumbo-jumbo to do it. Quite likely the problem this code had was orthogonality, or quite more likely, a bad maintainer.
Absence of OO(or pointers) becomes painfully obvious in large projects, so much so that many languages fake it. Anyway, VB error handling with a bunch of goto's is lame, generally speaking OO programming doesn't have goto's.
is not a shoulder hit ? as it is not a single stone right ?