473,386 Members | 1,793 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,386 software developers and data experts.

Conversion rules between unsigned operands and signed operand

Hi All,
I am trying to undestand "Type Conversions" from K&R book.I am not
able to understand the
bellow mentioned text
"Conversion rules are more complicated when unsigned operands are
involved. The problem
is that comparisons between signed and unsigned values are machine-
dependent, because
they depend on the sizes of the various integer types. For example,
suppose that int is 16 bits
and long is 32 bits. Then -1L < 1U, because 1U, which is an unsigned
int, is promoted to a
signed long. But -1L 1UL because -1L is promoted to unsigned long
and thus appears
to be a large positive number"
To understand it i wrote a small code

#include<stdio.h>
int main(void)
{
signed long sl = -5;
unsigned long ul= 5;
if (sl>ul)
{
printf("\n -5 is greater than 5\n");
}
else
{
printf("-5 is less than 5 \n");
}
return 0;
}

OP is
-5 is greater than 5
Could anybody help me to understand the conversion rules when
unsigned operands are involved ?

Regards,
Somenath

Jul 23 '07 #1
7 5013
somenath wrote:
>
Hi All,
I am trying to undestand "Type Conversions" from K&R book.I am not
able to understand the
bellow mentioned text
"Conversion rules are more complicated when unsigned operands are
involved. The problem
is that comparisons between signed and unsigned values are machine-
dependent, because
they depend on the sizes of the various integer types. For example,
suppose that int is 16 bits
and long is 32 bits. Then -1L < 1U, because 1U, which is an unsigned
int, is promoted to a
signed long. But -1L 1UL because -1L is promoted to unsigned long
and thus appears
to be a large positive number"
To understand it i wrote a small code

#include<stdio.h>
int main(void)
{
signed long sl = -5;
unsigned long ul= 5;
if (sl>ul)
{
printf("\n -5 is greater than 5\n");
}
else
{
printf("-5 is less than 5 \n");
}
return 0;
}

OP is
-5 is greater than 5
Could anybody help me to understand the conversion rules when
unsigned operands are involved ?
"rank" is the missing word here.
To compare two expressions, they must be converted to the same type.
The rule for comparing two exressions is simple,
and signed or unsigned types do not form any exceptions to this rule:
The lower ranking type is converted to the higher ranking type.

The above text about comparisons
being machine dependent because of sizes, is wrong.
For example, suppose that int and long are both 32 bits.
Then -1L < 1U, because 1U, which is an unsigned int,
is *converted* (not promoted) to a signed long,
and it has absolutely nothing to do with whether or not
int and long are the same size.

"Integer promotions" on the other hand, which are distinct
from the kind of conversions performed on an operand
of a relational operator, are dependent upon whether
or not type int can represent all the positive values
of the lower ranking type.

N869
6.3.1 Arithmetic operands
6.3.1.1 Boolean, characters, and integers
[#1] Every integer type has an integer conversion rank
defined as follows:
-- No two signed integer types shall have the same rank,
even if they have the same representation.
-- The rank of a signed integer type shall be greater than
the rank of any signed integer type with less
precision.
-- The rank of long long int shall be greater than the
rank of long int, which shall be greater than the rank
of int, which shall be greater than the rank of short
int, which shall be greater than the rank of signed
char.
-- The rank of any unsigned integer type shall equal the
rank of the corresponding signed integer type, if any.
-- The rank of any standard integer type shall be greater
than the rank of any extended integer type with the
same width.
-- The rank of char shall equal the rank of signed char
and unsigned char.
-- The rank of _Bool shall be less than the rank of all
other standard integer types.
-- The rank of any enumerated type shall equal the rank of
the compatible integer type (see 6.7.2.2).
-- The rank of any extended signed integer type relative
to another extended signed integer type with the same
precision is implementation-defined, but still subject
to the other rules for determining the integer
conversion rank.
-- For all integer types T1, T2, and T3, if T1 has greater
rank than T2 and T2 has greater rank than T3, then T1
has greater rank than T3.

/* BEGIN new.c */

#include<stdio.h>
#include<limits.h>

int main(void)
{
signed long sl = -5;
unsigned u = 5;

if (sl u) {
puts("-5 is greater than 5");
} else {
puts("-5 is less than 5");
}
printf("LONG_MAX is %ld\n", LONG_MAX);
printf("UINT_MAX is %u \n", UINT_MAX);
return 0;
}

/* END new.c */

On my machine the output of new.c is:
-5 is greater than 5
LONG_MAX is 2147483647
UINT_MAX is 4294967295

The unsigned type is converted to the long signed type,
even though on my machine,
they have the same size and number of bits.

--
pete
Jul 23 '07 #2
On Jul 23, 12:37 pm, pete <pfil...@mindspring.comwrote:
somenath wrote:
Hi All,
I am trying to undestand "Type Conversions" from K&R book.I am not
able to understand the
bellow mentioned text
"Conversion rules are more complicated when unsigned operands are
involved. The problem
is that comparisons between signed and unsigned values are machine-
dependent, because
they depend on the sizes of the various integer types. For example,
suppose that int is 16 bits
and long is 32 bits. Then -1L < 1U, because 1U, which is an unsigned
int, is promoted to a
signed long. But -1L 1UL because -1L is promoted to unsigned long
and thus appears
to be a large positive number"
To understand it i wrote a small code
#include<stdio.h>
int main(void)
{
signed long sl = -5;
unsigned long ul= 5;
if (sl>ul)
{
printf("\n -5 is greater than 5\n");
}
else
{
printf("-5 is less than 5 \n");
}
return 0;
}
OP is
-5 is greater than 5
Could anybody help me to understand the conversion rules when
unsigned operands are involved ?

"rank" is the missing word here.
To compare two expressions, they must be converted to the same type.
The rule for comparing two exressions is simple,
and signed or unsigned types do not form any exceptions to this rule:
The lower ranking type is converted to the higher ranking type.

The above text about comparisons
being machine dependent because of sizes, is wrong.
For example, suppose that int and long are both 32 bits.
Then -1L < 1U, because 1U, which is an unsigned int,
is *converted* (not promoted) to a signed long,
and it has absolutely nothing to do with whether or not
int and long are the same size.

"Integer promotions" on the other hand, which are distinct
from the kind of conversions performed on an operand
of a relational operator, are dependent upon whether
or not type int can represent all the positive values
of the lower ranking type.

N869
6.3.1 Arithmetic operands
6.3.1.1 Boolean, characters, and integers
[#1] Every integer type has an integer conversion rank
defined as follows:
-- No two signed integer types shall have the same rank,
even if they have the same representation.
-- The rank of a signed integer type shall be greater than
the rank of any signed integer type with less
precision.
-- The rank of long long int shall be greater than the
rank of long int, which shall be greater than the rank
of int, which shall be greater than the rank of short
int, which shall be greater than the rank of signed
char.
-- The rank of any unsigned integer type shall equal the
rank of the corresponding signed integer type, if any.
-- The rank of any standard integer type shall be greater
than the rank of any extended integer type with the
same width.
-- The rank of char shall equal the rank of signed char
and unsigned char.
-- The rank of _Bool shall be less than the rank of all
other standard integer types.
-- The rank of any enumerated type shall equal the rank of
the compatible integer type (see 6.7.2.2).
-- The rank of any extended signed integer type relative
to another extended signed integer type with the same
precision is implementation-defined, but still subject
to the other rules for determining the integer
conversion rank.
-- For all integer types T1, T2, and T3, if T1 has greater
rank than T2 and T2 has greater rank than T3, then T1
has greater rank than T3.

/* BEGIN new.c */

#include<stdio.h>
#include<limits.h>

int main(void)
{
signed long sl = -5;
unsigned u = 5;

if (sl u) {
puts("-5 is greater than 5");
} else {
puts("-5 is less than 5");
}
printf("LONG_MAX is %ld\n", LONG_MAX);
printf("UINT_MAX is %u \n", UINT_MAX);
return 0;

}

/* END new.c */

On my machine the output of new.c is:
-5 is greater than 5
LONG_MAX is 2147483647
UINT_MAX is 4294967295

The unsigned type is converted to the long signed type,
even though on my machine,
they have the same size and number of bits.

Hi Pete,
Many thanks for this information. But i am still not able to
understand the comparision.
As par my signed long has higher rank than unsigned int . so "u" will
be converted to
Signed long .Does it mean the value of "u" which is 5 will be
converted to -5 ?
Even then how "if (sl u)" is true ?

Regards,
Somenath
Jul 24 '07 #3
somenath wrote:
>
On Jul 23, 12:37 pm, pete <pfil...@mindspring.comwrote:
somenath wrote:
Hi All,
I am trying to undestand "Type Conversions" from K&R book.I am not
able to understand the
bellow mentioned text
"Conversion rules are more complicated when unsigned operands are
involved. The problem
is that comparisons between signed and unsigned values are machine-
dependent, because
they depend on the sizes of the various integer types. For example,
suppose that int is 16 bits
and long is 32 bits. Then -1L < 1U, because 1U, which is an unsigned
int, is promoted to a
signed long. But -1L 1UL because -1L is promoted to unsigned long
and thus appears
to be a large positive number"
To understand it i wrote a small code
#include<stdio.h>
int main(void)
{
signed long sl = -5;
unsigned long ul= 5;
if (sl>ul)
{
printf("\n -5 is greater than 5\n");
}
else
{
printf("-5 is less than 5 \n");
}
return 0;
}
OP is
-5 is greater than 5
Could anybody help me to understand the conversion rules when
unsigned operands are involved ?
"rank" is the missing word here.
To compare two expressions, they must be converted to the same type.
The rule for comparing two exressions is simple,
and signed or unsigned types do not form any exceptions to this rule:
The lower ranking type is converted to the higher ranking type.

The above text about comparisons
being machine dependent because of sizes, is wrong.
For example, suppose that int and long are both 32 bits.
Then -1L < 1U, because 1U, which is an unsigned int,
is *converted* (not promoted) to a signed long,
and it has absolutely nothing to do with whether or not
int and long are the same size.

"Integer promotions" on the other hand, which are distinct
from the kind of conversions performed on an operand
of a relational operator, are dependent upon whether
or not type int can represent all the positive values
of the lower ranking type.

N869
6.3.1 Arithmetic operands
6.3.1.1 Boolean, characters, and integers
[#1] Every integer type has an integer conversion rank
defined as follows:
-- No two signed integer types shall have the same rank,
even if they have the same representation.
-- The rank of a signed integer type shall be greater than
the rank of any signed integer type with less
precision.
-- The rank of long long int shall be greater than the
rank of long int, which shall be greater than the rank
of int, which shall be greater than the rank of short
int, which shall be greater than the rank of signed
char.
-- The rank of any unsigned integer type shall equal the
rank of the corresponding signed integer type, if any.
-- The rank of any standard integer type shall be greater
than the rank of any extended integer type with the
same width.
-- The rank of char shall equal the rank of signed char
and unsigned char.
-- The rank of _Bool shall be less than the rank of all
other standard integer types.
-- The rank of any enumerated type shall equal the rank of
the compatible integer type (see 6.7.2.2).
-- The rank of any extended signed integer type relative
to another extended signed integer type with the same
precision is implementation-defined, but still subject
to the other rules for determining the integer
conversion rank.
-- For all integer types T1, T2, and T3, if T1 has greater
rank than T2 and T2 has greater rank than T3, then T1
has greater rank than T3.

/* BEGIN new.c */

#include<stdio.h>
#include<limits.h>

int main(void)
{
signed long sl = -5;
unsigned u = 5;

if (sl u) {
puts("-5 is greater than 5");
} else {
puts("-5 is less than 5");
}
printf("LONG_MAX is %ld\n", LONG_MAX);
printf("UINT_MAX is %u \n", UINT_MAX);
return 0;

}

/* END new.c */

On my machine the output of new.c is:
-5 is greater than 5
LONG_MAX is 2147483647
UINT_MAX is 4294967295

The unsigned type is converted to the long signed type,
even though on my machine,
they have the same size and number of bits.

Hi Pete,
Many thanks for this information. But i am still not able to
understand the comparision.
As par my signed long has higher rank than unsigned int . so "u" will
be converted to
Signed long .Does it mean the value of "u" which is 5 will be
converted to -5 ?
Even then how "if (sl u)" is true ?
The answer is simple: I was wrong.
The rules are more complicated.
Both sl and u get converted to type long unsigned in the
above expression on my machine.
The reason is because on my machine,
signed long can't represent the entire range of unsigned values.

The conversion in question,
is called "the usual arithmetic conversions".

N869
6.3.1.8 Usual arithmetic conversions
[#1] Many operators that expect operands of arithmetic type
cause conversions and yield result types in a similar way.
The purpose is to determine a common real type for the
operands and result. For the specified operands, each
operand is converted, without change of type domain, to a
type whose corresponding real type is the common real type.
Unless explicitly stated otherwise, the common real type is
also the corresponding real type of the result, whose type
domain is the type domain of the operands if they are the
same, and complex otherwise. This pattern is called the
usual arithmetic conversions:
First, if the corresponding real type of either operand
is long double, the other operand is converted, without
change of type domain, to a type whose corresponding
real type is long double.
Otherwise, if the corresponding real type of either
operand is double, the other operand is converted,
without change of type domain, to a type whose
corresponding real type is double.
Otherwise, if the corresponding real type of either
operand is float, the other operand is converted,
without change of type domain, to a type whose
corresponding real type is float.
Otherwise, the integer promotions are performed on both
operands. Then the following rules are applied to the
promoted operands:
If both operands have the same type, then no
further conversion is needed.
Otherwise, if both operands have signed integer
types or both have unsigned integer types, the
operand with the type of lesser integer conversion
rank is converted to the type of the operand with
greater rank.
Otherwise, if the operand that has unsigned
integer type has rank greater or equal to the rank
of the type of the other operand, then the operand
with signed integer type is converted to the type
of the operand with unsigned integer type.
Otherwise, if the type of the operand with signed
integer type can represent all of the values of
the type of the operand with unsigned integer
type, then the operand with unsigned integer type
is converted to the type of the operand with
signed integer type.
Otherwise, both operands are converted to the
unsigned integer type corresponding to the type of
the operand with signed integer type.

--
pete
Jul 25 '07 #4
On Jul 25, 8:35 am, pete <pfil...@mindspring.comwrote:
somenath wrote:
On Jul 23, 12:37 pm, pete <pfil...@mindspring.comwrote:
somenath wrote:
Hi All,
I am trying to undestand "Type Conversions" from K&R book.I am not
able to understand the
bellow mentioned text
"Conversion rules are more complicated when unsigned operands are
involved. The problem
is that comparisons between signed and unsigned values are machine-
dependent, because
they depend on the sizes of the various integer types. For example,
suppose that int is 16 bits
and long is 32 bits. Then -1L < 1U, because 1U, which is an unsigned
int, is promoted to a
signed long. But -1L 1UL because -1L is promoted to unsigned long
and thus appears
to be a large positive number"
To understand it i wrote a small code
#include<stdio.h>
int main(void)
{
signed long sl = -5;
unsigned long ul= 5;
if (sl>ul)
{
printf("\n -5 is greater than 5\n");
}
else
{
printf("-5 is less than 5 \n");
}
return 0;
}
OP is
-5 is greater than 5
Could anybody help me to understand the conversion rules when
unsigned operands are involved ?
"rank" is the missing word here.
To compare two expressions, they must be converted to the same type.
The rule for comparing two exressions is simple,
and signed or unsigned types do not form any exceptions to this rule:
The lower ranking type is converted to the higher ranking type.
The above text about comparisons
being machine dependent because of sizes, is wrong.
For example, suppose that int and long are both 32 bits.
Then -1L < 1U, because 1U, which is an unsigned int,
is *converted* (not promoted) to a signed long,
and it has absolutely nothing to do with whether or not
int and long are the same size.
"Integer promotions" on the other hand, which are distinct
from the kind of conversions performed on an operand
of a relational operator, are dependent upon whether
or not type int can represent all the positive values
of the lower ranking type.
N869
6.3.1 Arithmetic operands
6.3.1.1 Boolean, characters, and integers
[#1] Every integer type has an integer conversion rank
defined as follows:
-- No two signed integer types shall have the same rank,
even if they have the same representation.
-- The rank of a signed integer type shall be greater than
the rank of any signed integer type with less
precision.
-- The rank of long long int shall be greater than the
rank of long int, which shall be greater than the rank
of int, which shall be greater than the rank of short
int, which shall be greater than the rank of signed
char.
-- The rank of any unsigned integer type shall equal the
rank of the corresponding signed integer type, if any.
-- The rank of any standard integer type shall be greater
than the rank of any extended integer type with the
same width.
-- The rank of char shall equal the rank of signed char
and unsigned char.
-- The rank of _Bool shall be less than the rank of all
other standard integer types.
-- The rank of any enumerated type shall equal the rank of
the compatible integer type (see 6.7.2.2).
-- The rank of any extended signed integer type relative
to another extended signed integer type with the same
precision is implementation-defined, but still subject
to the other rules for determining the integer
conversion rank.
-- For all integer types T1, T2, and T3, if T1 has greater
rank than T2 and T2 has greater rank than T3, then T1
has greater rank than T3.
/* BEGIN new.c */
#include<stdio.h>
#include<limits.h>
int main(void)
{
signed long sl = -5;
unsigned u = 5;
if (sl u) {
puts("-5 is greater than 5");
} else {
puts("-5 is less than 5");
}
printf("LONG_MAX is %ld\n", LONG_MAX);
printf("UINT_MAX is %u \n", UINT_MAX);
return 0;
}
/* END new.c */
On my machine the output of new.c is:
-5 is greater than 5
LONG_MAX is 2147483647
UINT_MAX is 4294967295
The unsigned type is converted to the long signed type,
even though on my machine,
they have the same size and number of bits.
Hi Pete,
Many thanks for this information. But i am still not able to
understand the comparision.
As par my signed long has higher rank than unsigned int . so "u" will
be converted to
Signed long .Does it mean the value of "u" which is 5 will be
converted to -5 ?
Even then how "if (sl u)" is true ?

The answer is simple: I was wrong.
The rules are more complicated.
Both sl and u get converted to type long unsigned in the
But does it mean -5 will be converted to 5 ? Even then how "if
(sl u)" is true ?

Jul 25 '07 #5
On Jul 25, 8:35 am, pete <pfil...@mindspring.comwrote:
somenath wrote:
On Jul 23, 12:37 pm, pete <pfil...@mindspring.comwrote:
somenath wrote:
Hi All,
I am trying to undestand "Type Conversions" from K&R book.I am not
able to understand the
bellow mentioned text
"Conversion rules are more complicated when unsigned operands are
involved. The problem
is that comparisons between signed and unsigned values are machine-
dependent, because
they depend on the sizes of the various integer types. For example,
suppose that int is 16 bits
and long is 32 bits. Then -1L < 1U, because 1U, which is an unsigned
int, is promoted to a
signed long. But -1L 1UL because -1L is promoted to unsigned long
and thus appears
to be a large positive number"
To understand it i wrote a small code
#include<stdio.h>
int main(void)
{
signed long sl = -5;
unsigned long ul= 5;
if (sl>ul)
{
printf("\n -5 is greater than 5\n");
}
else
{
printf("-5 is less than 5 \n");
}
return 0;
}
OP is
-5 is greater than 5
Could anybody help me to understand the conversion rules when
unsigned operands are involved ?
"rank" is the missing word here.
To compare two expressions, they must be converted to the same type.
The rule for comparing two exressions is simple,
and signed or unsigned types do not form any exceptions to this rule:
The lower ranking type is converted to the higher ranking type.
The above text about comparisons
being machine dependent because of sizes, is wrong.
For example, suppose that int and long are both 32 bits.
Then -1L < 1U, because 1U, which is an unsigned int,
is *converted* (not promoted) to a signed long,
and it has absolutely nothing to do with whether or not
int and long are the same size.
"Integer promotions" on the other hand, which are distinct
from the kind of conversions performed on an operand
of a relational operator, are dependent upon whether
or not type int can represent all the positive values
of the lower ranking type.
N869
6.3.1 Arithmetic operands
6.3.1.1 Boolean, characters, and integers
[#1] Every integer type has an integer conversion rank
defined as follows:
-- No two signed integer types shall have the same rank,
even if they have the same representation.
-- The rank of a signed integer type shall be greater than
the rank of any signed integer type with less
precision.
-- The rank of long long int shall be greater than the
rank of long int, which shall be greater than the rank
of int, which shall be greater than the rank of short
int, which shall be greater than the rank of signed
char.
-- The rank of any unsigned integer type shall equal the
rank of the corresponding signed integer type, if any.
-- The rank of any standard integer type shall be greater
than the rank of any extended integer type with the
same width.
-- The rank of char shall equal the rank of signed char
and unsigned char.
-- The rank of _Bool shall be less than the rank of all
other standard integer types.
-- The rank of any enumerated type shall equal the rank of
the compatible integer type (see 6.7.2.2).
-- The rank of any extended signed integer type relative
to another extended signed integer type with the same
precision is implementation-defined, but still subject
to the other rules for determining the integer
conversion rank.
-- For all integer types T1, T2, and T3, if T1 has greater
rank than T2 and T2 has greater rank than T3, then T1
has greater rank than T3.
/* BEGIN new.c */
#include<stdio.h>
#include<limits.h>
int main(void)
{
signed long sl = -5;
unsigned u = 5;
if (sl u) {
puts("-5 is greater than 5");
} else {
puts("-5 is less than 5");
}
printf("LONG_MAX is %ld\n", LONG_MAX);
printf("UINT_MAX is %u \n", UINT_MAX);
return 0;
}
/* END new.c */
On my machine the output of new.c is:
-5 is greater than 5
LONG_MAX is 2147483647
UINT_MAX is 4294967295
The unsigned type is converted to the long signed type,
even though on my machine,
they have the same size and number of bits.
Hi Pete,
Many thanks for this information. But i am still not able to
understand the comparision.
As par my signed long has higher rank than unsigned int . so "u" will
be converted to
Signed long .Does it mean the value of "u" which is 5 will be
converted to -5 ?
Even then how "if (sl u)" is true ?

The answer is simple: I was wrong.
The rules are more complicated.
Both sl and u get converted to type long unsigned in the
But does it mean -5 will be converted to 5 ? Even then how "if
(sl u)" is true ?

Jul 25 '07 #6
somenath wrote:
>
On Jul 25, 8:35 am, pete <pfil...@mindspring.comwrote:
somenath wrote:
On Jul 23, 12:37 pm, pete <pfil...@mindspring.comwrote:
somenath wrote:
Hi All,
I am trying to undestand "Type Conversions" from K&R book.I am not
able to understand the
bellow mentioned text
"Conversion rules are more complicated when unsigned operands are
involved. The problem
is that comparisons between signed and unsigned values are machine-
dependent, because
they depend on the sizes of the various integer types. For example,
suppose that int is 16 bits
and long is 32 bits. Then -1L < 1U, because 1U, which is an unsigned
int, is promoted to a
signed long. But -1L 1UL because -1L is promoted to unsigned long
and thus appears
to be a large positive number"
To understand it i wrote a small code
#include<stdio.h>
int main(void)
{
signed long sl = -5;
unsigned long ul= 5;
if (sl>ul)
{
printf("\n -5 is greater than 5\n");
}
else
{
printf("-5 is less than 5 \n");
}
return 0;
}
OP is
-5 is greater than 5
Could anybody help me to understand the conversion rules when
unsigned operands are involved ?
"rank" is the missing word here.
To compare two expressions, they must be converted to the same type.
The rule for comparing two exressions is simple,
and signed or unsigned types do not form any exceptions to this rule:
The lower ranking type is converted to the higher ranking type.
The above text about comparisons
being machine dependent because of sizes, is wrong.
For example, suppose that int and long are both 32 bits.
Then -1L < 1U, because 1U, which is an unsigned int,
is *converted* (not promoted) to a signed long,
and it has absolutely nothing to do with whether or not
int and long are the same size.
"Integer promotions" on the other hand, which are distinct
from the kind of conversions performed on an operand
of a relational operator, are dependent upon whether
or not type int can represent all the positive values
of the lower ranking type.
N869
6.3.1 Arithmetic operands
6.3.1.1 Boolean, characters, and integers
[#1] Every integer type has an integer conversion rank
defined as follows:
-- No two signed integer types shall have the same rank,
even if they have the same representation.
-- The rank of a signed integer type shall be greater than
the rank of any signed integer type with less
precision.
-- The rank of long long int shall be greater than the
rank of long int, which shall be greater than the rank
of int, which shall be greater than the rank of short
int, which shall be greater than the rank of signed
char.
-- The rank of any unsigned integer type shall equal the
rank of the corresponding signed integer type, if any.
-- The rank of any standard integer type shall be greater
than the rank of any extended integer type with the
same width.
-- The rank of char shall equal the rank of signed char
and unsigned char.
-- The rank of _Bool shall be less than the rank of all
other standard integer types.
-- The rank of any enumerated type shall equal the rank of
the compatible integer type (see 6.7.2.2).
-- The rank of any extended signed integer type relative
to another extended signed integer type with the same
precision is implementation-defined, but still subject
to the other rules for determining the integer
conversion rank.
-- For all integer types T1, T2, and T3, if T1 has greater
rank than T2 and T2 has greater rank than T3, then T1
has greater rank than T3.
/* BEGIN new.c */
#include<stdio.h>
#include<limits.h>
int main(void)
{
signed long sl = -5;
unsigned u = 5;
if (sl u) {
puts("-5 is greater than 5");
} else {
puts("-5 is less than 5");
}
printf("LONG_MAX is %ld\n", LONG_MAX);
printf("UINT_MAX is %u \n", UINT_MAX);
return 0;
}
/* END new.c */
On my machine the output of new.c is:
-5 is greater than 5
LONG_MAX is 2147483647
UINT_MAX is 4294967295
The unsigned type is converted to the long signed type,
even though on my machine,
they have the same size and number of bits.
Hi Pete,
Many thanks for this information. But i am still not able to
understand the comparision.
As par my signed
long has higher rank than unsigned int . so "u" will
be converted to
Signed long .Does it mean the value of "u" which is 5 will be
converted to -5 ?
Even then how "if (sl u)" is true ?
The answer is simple: I was wrong.
The rules are more complicated.
Both sl and u get converted to type long unsigned in the

But does it mean -5 will be converted to 5 ?
No. The converted expression is equal to ((long unsigned)-5).
Even then how "if
(sl u)" is true ?
The rule for converting a negative value to an unsigned integer type
is to add (1 + UNSIGNED_INTEGER_TYPE_MAX) repeatedly
to the negative value until it is not negative any more.

-5 gets converted to 4294967291LU

--
pete
Jul 25 '07 #7
On Jul 25, 3:35 pm, pete <pfil...@mindspring.comwrote:
somenath wrote:
On Jul 25, 8:35 am, pete <pfil...@mindspring.comwrote:
somenath wrote:
On Jul 23, 12:37 pm, pete <pfil...@mindspring.comwrote:
somenath wrote:
Hi All,
I am trying to undestand "Type Conversions" from K&R book.I am not
able to understand the
bellow mentioned text
"Conversion rules are more complicated when unsigned operands are
involved. The problem
is that comparisons between signed and unsigned values are machine-
dependent, because
they depend on the sizes of the various integer types. For example,
suppose that int is 16 bits
and long is 32 bits. Then -1L < 1U, because 1U, which is an unsigned
int, is promoted to a
signed long. But -1L 1UL because -1L is promoted to unsigned long
and thus appears
to be a large positive number"
To understand it i wrote a small code
#include<stdio.h>
int main(void)
{
signed long sl = -5;
unsigned long ul= 5;
if (sl>ul)
{
printf("\n -5 is greater than 5\n");
}
else
{
printf("-5 is less than 5 \n");
}
return 0;
}
OP is
-5 is greater than 5
Could anybody help me to understand the conversion rules when
unsigned operands are involved ?
"rank" is the missing word here.
To compare two expressions, they must be converted to the same type.
The rule for comparing two exressions is simple,
and signed or unsigned types do not form any exceptions to this rule:
The lower ranking type is converted to the higher ranking type.
The above text about comparisons
being machine dependent because of sizes, is wrong.
For example, suppose that int and long are both 32 bits.
Then -1L < 1U, because 1U, which is an unsigned int,
is *converted* (not promoted) to a signed long,
and it has absolutely nothing to do with whether or not
int and long are the same size.
"Integer promotions" on the other hand, which are distinct
from the kind of conversions performed on an operand
of a relational operator, are dependent upon whether
or not type int can represent all the positive values
of the lower ranking type.
N869
6.3.1 Arithmetic operands
6.3.1.1 Boolean, characters, and integers
[#1] Every integer type has an integer conversion rank
defined as follows:
-- No two signed integer types shall have the same rank,
even if they have the same representation.
-- The rank of a signed integer type shall be greater than
the rank of any signed integer type with less
precision.
-- The rank of long long int shall be greater than the
rank of long int, which shall be greater than the rank
of int, which shall be greater than the rank of short
int, which shall be greater than the rank of signed
char.
-- The rank of any unsigned integer type shall equal the
rank of the corresponding signed integer type, if any.
-- The rank of any standard integer type shall be greater
than the rank of any extended integer type with the
same width.
-- The rank of char shall equal the rank of signed char
and unsigned char.
-- The rank of _Bool shall be less than the rank of all
other standard integer types.
-- The rank of any enumerated type shall equal the rank of
the compatible integer type (see 6.7.2.2).
-- The rank of any extended signed integer type relative
to another extended signed integer type with the same
precision is implementation-defined, but still subject
to the other rules for determining the integer
conversion rank.
-- For all integer types T1, T2, and T3, if T1 has greater
rank than T2 and T2 has greater rank than T3, then T1
has greater rank than T3.
/* BEGIN new.c */
#include<stdio.h>
#include<limits.h>
int main(void)
{
signed long sl = -5;
unsigned u = 5;
if (sl u) {
puts("-5 is greater than 5");
} else {
puts("-5 is less than 5");
}
printf("LONG_MAX is %ld\n", LONG_MAX);
printf("UINT_MAX is %u \n", UINT_MAX);
return 0;
}
/* END new.c */
On my machine the output of new.c is:
-5 is greater than 5
LONG_MAX is 2147483647
UINT_MAX is 4294967295
The unsigned type is converted to the long signed type,
even though on my machine,
they have the same size and number of bits.
Hi Pete,
Many thanks for this information. But i am still not able to
understand the comparision.
As par my signed
long has higher rank than unsigned int . so "u" will
be converted to
Signed long .Does it mean the value of "u" which is 5 will be
converted to -5 ?
Even then how "if (sl u)" is true ?
The answer is simple: I was wrong.
The rules are more complicated.
Both sl and u get converted to type long unsigned in the
But does it mean -5 will be converted to 5 ?

No. The converted expression is equal to ((long unsigned)-5).
Even then how "if
(sl u)" is true ?

The rule for converting a negative value to an unsigned integer type
is to add (1 + UNSIGNED_INTEGER_TYPE_MAX) repeatedly
to the negative value until it is not negative any more.

-5 gets converted to 4294967291LU
But is this rules applies to largest negative number such as
-2147483648 ? then what will be the result when it is converted to
unsigned integer type?
Jul 30 '07 #8

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

9
by: Fred Ma | last post by:
Hello, I've been trying to clear up a confusion about integer promotions during expression evaluation. I've checked the C FAQ and C++ FAQ (they are different languages, but I was hoping one...
16
by: TTroy | last post by:
Hello, I'm relatively new to C and have gone through more than 4 books on it. None mentioned anything about integral promotion, arithmetic conversion, value preserving and unsigned preserving. ...
2
by: G Fernandes | last post by:
Hello, I have a question about using an unsigned int and a signed long int in an expression (where UINT_MAX > LINT_MAX). Based on the conversion rules, the unsigned int will be convered to...
14
by: junky_fellow | last post by:
Can anybody please explain this: When a value with integer type is converted to another integer type other than _Bool, if the new type is unsigned, the value is converted by repeatedly...
6
by: Gilles Rochefort | last post by:
Hello, I wrote the following code to wrap some existing C functions, and I get some warning about converting float to int. float zfactor; int tmp_x, corners_x; ...
6
by: sarathy | last post by:
Hi, What is integer promotion? How is it different from arithmetic conversion? Regards, Sarathy
6
by: NM | last post by:
I am given an int and have to tell whether the bit representation of that int is a palindrome or not. Here is what I have come up with bool isIntPalindrome(int num) { unsigned int temp = num;...
4
by: techie | last post by:
I have defined a number of unsigned integer types as follows: typedef unsigned char uint8; typedef unsigned short uint16; typedef unsigned int uint32; typedfe long long uint64; Is it...
6
by: Peter Lee | last post by:
what's the correct behaver about the following code ? ( C++ standard ) I got a very strange result.... class MyClass { public: MyClass(const char* p) { printf("ctor p=%s\n", p);
0
by: aa123db | last post by:
Variable and constants Use var or let for variables and const fror constants. Var foo ='bar'; Let foo ='bar';const baz ='bar'; Functions function $name$ ($parameters$) { } ...
0
by: ryjfgjl | last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
0
by: emmanuelkatto | last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud. Please let me know. Thanks! Emmanuel
1
by: nemocccc | last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
1
by: Sonnysonu | last post by:
This is the data of csv file 1 2 3 1 2 3 1 2 3 1 2 3 2 3 2 3 3 the lengths should be different i have to store the data by column-wise with in the specific length. suppose the i have to...
0
by: Hystou | last post by:
There are some requirements for setting up RAID: 1. The motherboard and BIOS support RAID configuration. 2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
0
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
0
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers,...
0
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.