Linked by Thom Holwerda on Mon 3rd Sep 2012 20:46 UTC, submitted by MOS6510
General Development I like this one: "By definition, a program is an entity that is run by the computer. It talks directly to the CPU and the OS. Code that does not talk directly to the CPU and the OS, but is instead run by some other program that does talk directly to the CPU and the OS, is not a program; it's a script." Here's the other eleven.
Thread beginning with comment 533751
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by Soulbender
by Soulbender on Tue 4th Sep 2012 04:12 UTC in reply to "RE: Comment by Soulbender"
Member since:

Or really anything that doesn't turn your execution order into spaghetti.

Good thing that is impossible to do with return values, eh?

The author was lamenting the simple fact that OO is too vague.

Seriously, what does it matter? As long as the OO model in the language you use makes sense and you know when to use and when not to.

Reply Parent Score: 3

satsujinka Member since:

None of the things I mentioned do it by default (you have to make the decision to have spaghetti code.) try/catch/finally does it by default. That's the whole reason you people use it.

The definition of OO matters when we want to have serious discussions about it. It's sort of hard to judge the merits of something that lacks a solid definition.

Reply Parent Score: 1

Soulbender Member since:

That's the whole reason you people use it.

"you people"?

Reply Parent Score: 3

Soulbender Member since:

try/catch/finally does it by default

Try/catch does not automatically create spaghetti code any more than return values and message structures.

Reply Parent Score: 4