On Tue, Apr 7, 2015 at 8:36 AM, <jonas.thornv...@gmail.com> wrote: > Den tisdag 7 april 2015 kl. 16:30:15 UTC+2 skrev Denis McMahon: >> On Tue, 07 Apr 2015 09:29:59 -0400, Dave Angel wrote: >> >> > On 04/07/2015 05:44 AM, jonas.thornv...@gmail.com wrote: >> >> >> I want todo faster baseconversion for very big bases like base 1 000 >> >> 000, so instead of adding up digits i search it. >> >> > How do you know the baseconversion is the bottleneck, if you haven't >> > written any Python code yet? >> >> He doesn't. He doesn't comprehend that as far as a computer is concerned >> an integer has no specific 'base', it's only when presented in a form for >> humans to read that it gets base information added in the representation. >> >> He's making these and other similar errors in the javascript groups too. >> >> I suspect he's one of those people that spends his time thinking up >> elaborate solutions that he has no idea how to implement as a response to >> dreamt up non existent problems. >> >> -- >> Denis McMahon, denismfmcma...@gmail.com > > Bullshit declare two integers in any language one 7 and one 4 and then write > x=7+4; if you find a programming language where that does not yield 11 tell > me. > > Integers are internally assumed to be base 10 otherwise you could not > calculate without giving the base. > > All operations on integers addition, subtraction, multiplication and division > assume base 10.
You're conflating the internal representation of the integer with the formatting that is done to display the integer. When you do "print(x)", the computer doesn't just dump the internal representation of x onto the display. It formats x as character data and displays *that*. For integers, the vast majority of programming languages will do the formatting as base 10 by default, since that is the format preferred by most humans. -- https://mail.python.org/mailman/listinfo/python-list
