"... $COLOR in color."
One peeve some have is about color descriptions. "It was orange in color." is redundant since orange is clearly the color and "It was orange" conveys the same information. I just noticed a situation where the "..in color" line makes sense. While for most colors it is redundant there are some where it conveys necessary information. "The brick was gold in color." has a different meaning than "The brick was gold." The same applies to silver. Color names that are also material names need to be distinguished between mere color and actual material - at least in some cases. If the item described is clearly not the material ("The sunbather's skin was bronze."), then the argument against redundancy returns.
no subject
.....and that is probably not even what you are talking about is it?
Creeps away.
no subject
No, it's not what I was going on about. The "It was orange in color." vs. "It was orange." is a matter of writing style. In both cases the color information (something is orange) is there.
I had a college roommate once who had a color blindness. He once had me write "pink" and "purple" on a couple items of his as he couldn't tell them apart otherwise (and his "friends" delighted in taking one away and requiring him to ask for its return by color...) He said that the color blindness wasn't entirely a bad thing, as when he went hunting the usual animal camouflage simply didn't exist for him - he thought things were rather obvious.
no subject
no subject
I listen to Car Talk on MPR, so I get both at once!
no subject
if (woofp == TRUE)
....
if (arfp == FALSE)
....
or worse yet,
if (mumble != TRUE)
....
I can't help being reminded of Tarski's definition of truth: the proposition "snow is white" is true if and only if snow is white.
Do people who code this way talk this way? "If the truth value of the proposition "the movie runs longer than two hours" is true, I'll call you."
no subject
Aside from the curious character of Dover in the Suburban Jungle (http://www.suburbanjungle.com/d/19990322.html) comic strip, I have my doubts.
no subject
typedef BOOL int;
#define TRUE -1 /* Or some other, non-zero constant */
#define FALSE 0
BOOL bResult1 = FunkyFunction();
bool bResult2 = FunkyFunction();
For bResult2, it can only have the values "true" and "false". For bResult1, it is possible to have a non-zero value that isn't TRUE. So:
if (bResult1) DoFoo();
if (bResult1 == TRUE) DoBar();
Means that DoFoo() may be called in cases where DoBar() would not.
Personally, I really like Python's definition. 0-length strings, empty lists, empty tuples, the value 0, the value False, and the None value are all considered false. All other values are true.
Bah, look what you made me do! I've spewed geekery all over Vakko's LJ entry.
no subject
no subject
no subject
Turkles is silly.
no subject
no subject
Most of the time, though, you're right; it's simply redundancy, perpetrated by someone too ignorant to know better or too careless to be concerned about word usage.