What happens when I assign long int to int in C?

by

The language guarantees that int is at least 16 bits, long is at least 32 bits, and long can represent at least all the values that int can represent.

If you assign a long value to an int object, it will be implicitly converted. There’s no need for an explicit cast; it would merely specify the same conversion that’s going to happen anyway.

On your system, where int and long happen to have the same size and range, the conversion is trivial; it simply copies the value.

On a system where long is wider than int, if the value won’t fit in an int, then the result of the conversion is implementation-defined. (Or, starting in C99, it can raise an implementation-defined signal, but I don’t know of any compilers that actually do that.) What typically happens is that the high-order bits are discarded, but you shouldn’t depend on that. (The rules are different for unsigned types; the result of converting a signed or unsigned integer to an unsigned type is well defined.)

If you need to safely assign a long value to an int object, you can check that it will fit before doing the assignment:

#include <limits.h> /* for INT_MIN, INT_MAX */

/* ... */

int i;
long li = /* whatever */

if (li >= INT_MIN && li <= INT_MAX) {
    i = li;
}
else {
    /* do something else? */
}

The details of “something else” are going to depend on what you want to do.

One correction: int and long are always distinct types, even if they happen to have the same size and representation. Arithmetic types are freely convertible, so this often doesn’t make any difference, but for example int* and long* are distinct and incompatible types; you can’t assign a long* to an int*, or vice versa, without an explicit (and potentially dangerous) cast.

And if you find yourself needing to convert a long value to int, the first thing you should do is reconsider your code’s design. Sometimes such conversions are necessary, but more often they’re a sign that the int to which you’re assigning should have been defined as a long in the first place.

More Related Contents:

  1. Can I compare int with size_t directly in C?
  2. Assignment makes pointer from integer without a cast and vice versa in c
  3. How to convert an int to string in C?
  4. Dividing 1/n always returns 0.0 [duplicate]
  5. printf(“%p”) and casting to (void *)
  6. Check if input is integer type in C
  7. Should I explicitly cast malloc()’s return value? [duplicate]
  8. How do I check if an integer is even or odd? [closed]
  9. How to convert integer to string in C? [duplicate]
  10. Question about C behaviour for unsigned integer underflow
  11. How can I cast int to enum in C#?
  12. Array Type – Rules for assignment/use as function parameter
  13. Efficient unsigned-to-signed cast avoiding implementation-defined behavior
  14. printf specify integer format string for float
  15. When is casting between pointer types not undefined behavior in C?
  16. Casting one struct pointer to another – C
  17. C: Casting minimum 32-bit integer (-2147483648) to float gives positive number (2147483648.0)
  18. casting char[][] to char** causes segfault?
  19. Casting a pointer does not produce an lvalue. Why?
  20. C integer overflow
  21. What is the conversion specifier for printf that formats a long?
  22. Why / when to use `intptr_t` for type-casting in C?
  23. Casting one C structure into another
  24. Pointer initialisation gives segmentation fault
  25. Why is 248×248 the maximum bi dimensional array size I can declare?
  26. How to print the name of the symbols of ELF files like the nm?
  27. C usual arithmetic conversions
  28. What’s the difference between “int” and “int_fast16_t”?
  29. C Function to Convert float to byte array
  30. Is typecast required in malloc? [duplicate]

Leave a Comment