negative-number

1/2 gives 0 as it should. However, -1/2 gives -1 , but I want it to round towards 0 (i.e. I want -1/2 to be 0), regardless of whether it's positive or negative. What is the best way to do that? Do floating point division then convert to an int. No extra modules needed. >>> int(float(-1)/2) 0 >>> int(float(-3)/2) -1 >>> int(float(1)/2) 0 >>> int(float(3)/2) 1 dawg Python's default division of integers is return the floor (towards negative infinity) with no ability to change that. You can read the BDFL's reason why. To do 'round up' division, you would use: >>> a=1 >>> b=2 >>> (a+(-a%b))//b 1 >>

I have a hex string that represents a 2's complement number. Is there an easy way (libraries/functions) to translate the hex into a decimal without working directly with its bits?? E.G. This is the expected output given the hex on the left: "0000" => 0 "7FFF" => 32767 (max positive number) "8000" => -32768 (max negative number) "FFFF" => -1 Thanks! This seems to trick java into converting the number without forcing a positive result: Integer.valueOf("FFFF",16).shortValue(); // evaluates to -1 (short) Of course this sort of thing only works for 8, 16, 32, and 64-bit 2's complement: Short

I use python 2.6 >>> hex(-199703103) '-0xbe73a3f' >>> hex(199703103) '0xbe73a3f' Positive and negative value are the same? When I use calc, the value is FFFFFFFFF418C5C1 . Python's integers can grow arbitrarily large. In order to compute the raw two's-complement the way you want it, you would need to specify the desired bit width. Your example shows -199703103 in 64-bit two's complement, but it just as well could have been 32-bit or 128-bit, resulting in a different number of 0xf 's at the start. hex() doesn't do that. I suggest the following as an alternative: def tohex(val, nbits): return

This question already has an answer here: Why do these two multiplication operations give different results? 2 answers I'm attempting to calculate 30 days by multiplying milliseconds however the result continually ends up being a negative number for the value of days_30 and I'm not sure why. Any suggestions are greatly appreciated! CODE SNIPPET: // check to ensure proper time has elapsed SharedPreferences pref = getApplicationContext() .getSharedPreferences("DataCountService", 0); long days_30 = 1000 * 60 * 60 * 24 * 30; long oldTime = pref.getLong("smstimestamp", 0); long newTime = System

Ok so I'm working on a program that takes in an image, isolates a block of pixels into an array, and then gets each individual rgb value for each pixel in that array. When I do this //first pic of image //just a test int pix = myImage.getRGB(0,0) System.out.println(pix); It spits out -16106634 I need to get the (R, G, B) value out of this int value Is there a formula, alg, method? The BufferedImage.getRGB(int x, int y) method always returns a pixel in the TYPE_INT_ARGB color model. So you just need to isolate the right bits for each color, like this: int pix = myImage.getRGB(0, 0); int r =

Questions arise when I type in these expressions to Python 3.3.0 -10 // 3 # -4 -10 % 3 # 2 10 // -3 # -4 10 % -3 # -2 -10 // -3 # 3 It appears as though it takes the approximate floating point (-3.33)? and rounds down either way in integer division but in the modulo operation it does something totally different. It seems like it returns the remainder +/-1 and only switches the sign depending on where the negative operand is. I am utterly confused, even after looking over other answers on this site! I hope someone can clearly explain this too me! The book says hint: recall this magic formula a

I'm learning about function overloading in C++ and came across this: void display(int a) { cout << "int" << endl; } void display(unsigned a) { cout << "unsigned" << endl; } int main() { int i = -2147483648; cout << i << endl; //will display -2147483648 display(-2147483648); } From what I understood, any value given in the int range (in my case int is 4 byte) will call display(int) and any value outside this range will be ambiguous (since the compiler cannot decide which function to call). It is valid for the complete range of int values except its min value i.e. -2147483648 where compilation