Will "long i = 1;" cause an implicit type conversion in C?

Question

If I write "long i = 1;" instead of "long i = 1l;", will the 1 be recognized as int and then implicitly converted to long?

Edit: Thank you all. I see there's no type conversion. Is this also the case with the suffix u (like 10u)? Then what's the use of those l and u?

Answer 1

Most modern compilers should be smart enough to see that you're assigning the literal to a long, and will make the literal of that type instead of forcing a pre-assignment conversion.

Answer 2

Today's compilers will recognize it and generate the same result.

Answer 3

Pretty sure that if written exactly as stated, it will be equivalent to i = 1l; Any conversion will be done at compile time.

However, if you write

long i = (unsigned int)-1;

then i will probably not be what you expected.

Answer 4

The compiler will see what you are trying to assign and set the value to 1 immediately. There is no type conversion that happens with a literal. Even if you said long x = 1.0, you won't see a runtime type conversion.

By the way, on Windows, long and int are the same so there wouldn't be a type conversion anyway.

[Edit: made last comment specific to Windows; removed reference to preprocessor]

Answer 5

The type of the constant 1 is int, so technically a type conversion will be done but it'll be done at compile time and nothing is lost.

However, consider the more interesting example of:

int main(void)
{
    long long i = -2147483648;
    long long j = -2147483647 - 1;

    printf( " i is %lld, j is %lld\n", i, j);

    return(0);
}

I get the following results from various compilers:

• MSCV 9 (Version 15.00.21022.08):

              i is 2147483648, j is -2147483648
  

• GCC (3.4.5):

              i is -2147483648, j is 0
  

• Comeau (4.3.10.1):

              i is 2147483648, j is -2147483648
  

• Digital Mars:

              i is -2147483648, j is -2147483648
  

I'm not sure yet how to account for the differences. It could be one or more of:

• compiler bugs
• C90 vs. C99 rules in operand promotion ("long long" support is C99, but some of these compilers might be compiling for C90 with "long long" as an extension)
• implementation defined behavior
• undefined behavior

FWIW, the behavior of MSVC and Comeau is what I expected - which is something that many might still find surprising. The logic (in my mind) for the first operation is:

• -2147483648 gets tokenized as '-' and 2147483648
• 2147483648 is an unsigned int (since it can't fit into an int - I believe this is different in C99)
• applying the unary '-' operator results in 2147483648 again due to unsigned arithmetic rules
• converting that into a long long doesn't change the sign.

The logic for the second operation is:

• -2147483647 gets tokenized as '-' and 2147483647
• 2147483647 is a signed int
• subtracting 1 results in -2147483648 since there's no problem representing that number
• converting that into a long long doesn't change the sign.