Direct casting types don't have to be strictly related It comes in all types of flavors Usually a new object is created Copy and information might be lost Change reference type, otherwise throws exception. Regarding use for casting, you still see the need for it in some libraries
Had you been doing just double x = a;, you can do away with the explicit conversion since an int is implicitly converted to a double (live example). Do you understand the concept of casting Casting is the process of type conversion, which is in java very common because its a statically typed language Proper way of casting pointer types asked 12 years, 7 months ago modified 1 year ago viewed 128k times Casting has sense only for a variable (= chunk of memory whose content can change) there are no variables whose content can change, in python There are only objects, that aren't contained in something
Then, the type of an object can't change, afaik Then, casting has no sense in python That's my believing and opinion Correct me if i am wrong, please 'casting' with reflection asked 16 years, 1 month ago modified 4 years, 6 months ago viewed 65k times The real question is what you want to do when/if the value in the unsigned int it out of the range that can be represented by a signed int
If it's in range, just assign it and you're done If it's out of range, that'll give an unspecified result so you'll probably want to reduce it the right range first, or assign it to a larger signed type.
WATCH
