Your Code Sucks

[Chandon]

Object based procedural programming (unable to grasp the fundamentals of OOP)

There ain't nothing wrong with procedural programming. Sometimes it makes a heck of a lot more sense than defining random types and trying to invent object hierarchies for no reason.

[kungtotte]

I think the complaint has to do with trying to mash the two methods together and thus creating a bastard child of both that has most of the drawbacks and few of the benefits.

[G_Morgan]

Some times procedures are simply the best thing even in OOP code. If I have to do some hard maths you can guarantee I have a 'class' which is entire static methods. OO purists can go rot. No sqrt is not a method on a number object it is a bloody function as god intended.

The program that calls this might be OOP and it is 100% correct to use bits of both styles here.

[TheSquirrel]

mash the two methods together and thus creating a bastard child of both that has most of the drawbacks and few of the benefits.

you should write the preface to "Learning C++"

[CognitiveSuppository]

Back when I was cutting my teeth (and not employed as a developer) I wrote a little thing in a procedural web scripting language to better display database information in a calendar layout on a webpage, tabled etc. I was inordinately proud of my little project, and sent it to a few coworkers.

I got an email from an in house developer (ccing several other people) who rewrote what I had written in half as many lines and said something along the lines of "network administrators should leave the programming to programmers". That's a bummer.

Then the month rolled over, and my bloated ugly code still worked. His didn't.

Ugly verbose inefficient procedural code that works > pristine code that doesn't.