LSB & Posix Conflicts
An anonymous reader writes "The OpenGroup has published a detailed list of the conflicts between the Linux Standards Base and Posix ? that is accessible through their website. "
← Back to Stories (view on slashdot.org)
> We had better fix this. I'll go ask SCO what to do.
SCO: All your Linux Standard Base are belong to us.
If you were blocking sigs, you wouldn't have to read this.
I find the misues of such a word by a programmer to be quite funny, since programmers can quite often be quite excellent with the written language.
In fact, I know a few English majors that turned out to be exceptional programmers, since programming is simply a combination of imagination and learning the rules, complex or otherwise, of a new language. This isn't much of a leap from learning the rules of the English language.
Yeah, go ahead and mod me off-topic, ignore the thread I am responding to why don't you...
If you ignore the other uses of a tool, does that make the tool less useful, or you less useful?
Computer instructions include arithmetic operations such as ADD or SUB.
Computer instructions include logical operations such as AND or OR.
Logical AND is maybe a bit redundant, (illogical AND?), but avoids confusion as a synonym for ADD as in "2 and 2 are 4".
& is a binary operator which produces the logical AND of its two evaluated parameters.
&& is a flow control operator which evaluates its right-hand parameter only if required to determine the truth value. This is NOT what was referred to.
ASM goes something like:
LOAD flags
AND FLAG_CONSTANT
JZ around_blah
C could be as simple as:
if ( flags & FLAG_CONSTANT ) { blah ; }