Procedural programming with the use of objects is the most applicable to any situation. Pure object oriented is slow and logically ambiguous at times, pure procedural programing is mysterious and far too intricate.

I like objects... inheritance is very useful - It's too bad that I have not really been using it to its full advantage type thingy.

I agree with nitrus. OO with a splash of procedural makes for easier time of writing and usually understanding the code. OO is great because of its reusablity, but it suffers because of it's abstraction at times. Er, I think.

Anyways.

Objects suck. Speically if you were never taught how to program in OOP. But im a big fan of procedural. It acutally makes sense. To me. Maybe not to anyone else, but who cares.

Pitty we don't have any Java buffs on here, they'd be freaking out...

OOP programming was supposed to be the wave of the future. Back when it first appeared, everyone was convinced that object reuse was the way to go.

I've been programming for over ten years now. Do you think I've ever dragged out an old piece of code to use within another project?!? Not a chance. Unless you really have a powerfull inner eye that can forecast the future the objects usually tend to never blend nicely.

On a side note, when I was using C, if you were really insane, you could align all of your structures in such a way that inheritance was as easy as changing the type cast of the same memory segment. Try that in your spare time!

Today I prefer to create objects for generic use, and use procedural methodology for the event handlers. You can call me lazy, but I've yet to figure out an elegant way to wrap OOP around event generation. It's an added layer of complexity that I'd rather aviod. Ah... if only we could go back to the days of assembly programming. NOT!