Python is a very exact structured language. If you take care that at least one of the constituents of a division is a clearly recognizeable floating point number, it will apply floating point divison, else integer division (with truncation), making it much faster. Of course, I would also be reluctant to specify encoder counts as 200.000 instead of plain 200, fearing rounding errors from division, but these are obviously less dangerous than truncation errors.
Peter Am 15.02.2014 03:59, schrieb Charles Steinkuehler: > > Not that this is the problem, but I've had a horrible time with Python > and floating point numbers. Python is always wanting to default to > integers, and frequently truncates intermediate results to integers > causing subtle issues with the resulting output that leaves me > head-scratching for a while. I think _every_ bit of python code I've > worked with has had this issue at least once... > > ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
