The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Apparently they are really good at using a certain UNIX editor, they are VI-kings!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
property, attribute are mostly interchangeable AFAIK
disagree, it's contextually dependent.
Example: a yellow banana
property: banana - it can not be anything else (excluding if destroyed)
attribute: color: yellow - the color of the banana can change - left alone will become brown, black, slime, destroyed
but the color itself (not color of the banana) is a property. yellow is yellow, it can be no other.
Only if the only thing you are going to do with fruit is classify them. If fruits have behavior, then banana is a derived class of fruit, and color is an attribute of banana. Your solution isn't very object oriented.
If you have a property, you will have to pay a tribute
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
Last Visit: 21-Sep-20 5:41 Last Update: 21-Sep-20 5:41