OO vs procedural

Tell me about it.

I came here in 2009 because someone I met told me about a like totally cool and underground forum called 4chan /b/. True story.

>>81
And you've accomplished so much since that time. Not really, but I thought I'd try to make you less pathetic than what you are.

>>79
Same, except I'm older than you (turning 14 soon) :p. I'm also interested in hacking. I want to form a group and troll shitty sites XD

>>41
>ID:Heaven

wat.

>>84
We used to have IDs associated with our posts in 2007.

>>85
Forced IDs should be on every board. Or hell, even a limit of like 3-5 new threads per day, it would cut out 95% of the spam.

Bringing /prog/ back to its people
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy

OO is just a superset of procedural programming with some simplifications for things that you'd do anyway without them (functions taking pointers to structs -> logically put them together with the data in the struct definition, add the "this" pointer and all the struct members in scope automatically.)

It's all a bunch of terminology made to make things look new and interesting when it's really nothing more than a way to simplify existing convention.