"Condition is Always False" Question

[Brian]

I am using Borland C++ Builder 5 for my application. When I build my
application, it states that I have several if-statements that will
always be false. The statements appear correct, so could someone
please enlighten me as to how C++ Builder may think that the
conditions will always be false. See below. Thanks.

<snip>
td.expMon = trk2[9] * 10 + trk2[10];

// Borland says this is always false, though the condition is
fine.
if ((td.expMon < 0) || (td.expMon 12)) {
err = TKT_INVALID_MON TH;
}
</snip>

<snip>
td.expDay = trk2[11] * 10 + trk2[12];

// Borland says this is always false, though the condition is
fine.
if ((td.expDay < 0) || (td.expDay 31)) {
err = TKT_INVALID_DAY ;
}
</snip>

<snip>
td.eftvDay = trk2[28] * 10 + trk2[29];
// Borland says this is always false, though the condition is
fine.
if ((td.eftvDay < 0) || (td.eftvDay 31)) {
err = TKT_INVALID_DAY ;
}
</snip>

[Marcus Kwok]

Rolf Magnus <ra******@t-online.dewrote:

Marcus Kwok wrote:

>Victor Bazarov <v.********@com acast.netwrote:

>>C++ supports three representations at this time: 2's complement, 1's
complement and signed magnitude.

I don't doubt you (you have demonstrated that you have much greater
knowledge of the standard than I do), but I am surprised by this. I
would have thought that with C++'s goal of being portable to many
architecture s, it would allow for a biased representation[0] for
numbers.

It requires that the bit combination for positive integers is the same for
signed and unsigned types.

OK, then this would disqualify the biased representation (unless the
bias is 0, which doesn't give you anything usefully different). Thanks.

--
Marcus Kwok
Replace 'invalid' with 'net' to reply